- NitLink setup starts with a Windows PC, compatible capture card, console, and display.
- Connect the HDMI path before launching NitLink so Windows can initialize the capture device.
- Check WebView2 and DirectX 11 when preparing the Windows environment.
- Test SDR first, then enable HDR, VRR, or advanced pixel formats separately.
- Use official releases from the NitLink GitHub Releases page or Steam listing.
NitLink Setup Requirements
NitLink is a Windows capture-card viewer for displaying a console signal in a desktop window. A successful setup depends on the full signal path: console, HDMI cables, capture card, Windows computer, graphics hardware, and display. Prepare each part before opening the application.
The official project information identifies a DirectX 11-capable GPU and Microsoft WebView2 as important Windows requirements. HDR and VRR also depend on the capabilities of the source, capture card, graphics output, and monitor. Advanced features should be tested only after a basic video feed is working.
| Component | Basic requirement | Setup purpose |
|---|---|---|
| Windows PC | Windows system with a compatible GPU | Runs NitLink and presents the captured image |
| Graphics hardware | DirectX 11-capable GPU | Supports rendering and display output |
| Capture card | Windows-recognized USB or PCIe device | Receives the console video signal |
| Console | HDMI video output | Provides the source image and audio |
| Display | Standard monitor; HDR or VRR model for advanced features | Shows the NitLink window |
| Software | NitLink release and WebView2 | Provides the application and interface environment |
Console Source
Connect the console HDMI output to the capture card input. Turn the console on before selecting the source in NitLink.
Capture Device
Use a capture card that appears as an available video device in Windows. Elgato 4K Pro, 4K X, and 4K S are among the devices identified for support or verification.
Windows Host
Keep the capture card connected directly to the computer when possible. Allow Windows time to initialize the device before launching the viewer.
Viewing Display
Use a normal display for the first test. Add HDR or VRR only after the standard SDR signal is visible and stable.
Start with the simplest signal path: standard resolution, SDR output, and one display. This makes it easier to identify whether a problem comes from the cable, capture card, Windows, or advanced display settings.
Connect the Console and Capture Card
The physical connection determines whether NitLink can receive a usable signal. Most setups send the console HDMI output into the capture card, then connect the capture card to Windows through USB or PCIe. A capture card with HDMI pass-through can also send the signal to a television or monitor while NitLink displays the same source in a Windows window.
Keep the first connection test direct. Avoid adding splitters, receivers, switchers, or unusual adapters until the basic path works. If the capture card is not visible in Windows, NitLink cannot select it as a source.
| Connection stage | Cable or port | What to confirm |
|---|---|---|
| Console to capture card | Console HDMI output to capture input | The input receives an active signal |
| Capture card to Windows | USB or installed PCIe connection | Windows recognizes the device |
| Optional pass-through | Capture output to television or monitor | The display supports the same signal mode |
| Windows to monitor | GPU output to display | The NitLink window has a usable destination |
| Audio path | HDMI audio through the capture device | Audio is available to the selected output |
Power on the Console
Turn on the console and wait for its normal home screen or active output. A live source makes it easier to confirm whether the capture card is receiving video.
Connect HDMI Input
Connect the console HDMI output to the capture card HDMI input. Check the port labels carefully because an input and pass-through output may look similar.
Connect the Capture Card to Windows
Attach the USB cable or install the PCIe capture card according to its hardware requirements. Use a direct computer connection for the initial test rather than an unpowered hub.
Add Pass-Through When Needed
If you want to play on a separate television or monitor, connect the capture card pass-through output to that display. Confirm that the display mode is supported by the card.
Wait for Device Detection
Give Windows time to initialize the capture device. Check available video devices before opening NitLink, especially after changing USB ports or reconnecting the card.
Do not assume that a pass-through display proves the Windows capture path is working. Pass-through and USB or PCIe capture can use different parts of the device, so test the NitLink source separately.
Install and Launch NitLink on Windows
NitLink is distributed through official channels, including the project’s GitHub Releases page and Steam listing. The portable GitHub release workflow generally involves downloading the Windows archive, extracting it, and launching NitLink.exe. Use the official release page rather than an unofficial mirror or republished executable.
The Steam version provides another official distribution option and includes experimental Frame Generation functionality. For a basic capture-card setup, first confirm that the application can display the source before exploring optional performance features.
| Distribution | Typical workflow | Best use |
|---|---|---|
| GitHub Releases | Download the Windows archive, extract it, launch NitLink.exe | Portable official release |
| Steam listing | Install through the official Steam page | Store-based installation and library access |
| Unofficial mirror | Avoid | File authenticity and update status are uncertain |
- Open the official NitLink GitHub Releases page.
- Select the current Windows release asset.
- Save the archive to a local folder.
- Extract the archive to a location you can access easily.
- Launch
NitLink.exe. - If Windows shows a security prompt, verify that the file came from the official release channel before proceeding.
- Select the available capture source inside NitLink.
- Confirm that the console image appears before changing HDR, VRR, or frame-presentation options.
First Launch Checklist:
- Download NitLink from an official release channel
- Extract the Windows package to a local folder
- Confirm the capture card is visible in Windows
- Launch NitLink after the console is producing a signal
- Select the correct capture source
- Verify that video appears in the application window
The first successful milestone is a stable console image in the NitLink window. Save advanced settings for later so you have a reliable baseline for comparison.
Configure Display, Audio, HDR, and VRR
After the video feed appears, adjust NitLink for the display and listening setup. Window mode is useful for testing because it lets you keep Windows controls, chat, OBS, or other tools visible. Full screen is better for focused viewing, while picture-in-picture can keep the console feed above other desktop windows.
Configure one major feature at a time. HDR changes image format and brightness behavior, while VRR changes display timing. Testing them separately makes it easier to identify a color-range mismatch, unsupported pixel format, or refresh-rate conflict.
| Goal | Recommended starting point | What to watch |
|---|---|---|
| Basic viewing | Window mode, SDR, standard refresh rate | Stable image and correct aspect ratio |
| Low latency | Low Latency enabled, appropriate VSync setting | Responsiveness versus tearing |
| 30 FPS source | Matched Present Cap and even frame pacing | Uneven motion or repeated frames |
| HDR viewing | Windows HDR enabled with HDR display mode | Gray blacks, washed highlights, wrong colors |
| VRR viewing | Compatible display with output inside VRR range | Flicker, tearing, or unstable refresh |
| Multitasking | Picture-in-picture | Window position and visibility |
| Focused play | Full screen | Scaling and display mode behavior |
For low-latency use, enable NitLink’s Low Latency mode and evaluate VSync according to the display behavior. Competitive games may benefit from a responsive presentation path, while 30 FPS console games often look better when frame pacing is matched to the source. A Present Cap can help align output timing or keep a VRR display below its maximum refresh rate.
For HDR, check the complete chain:
- Confirm whether the console is sending SDR or HDR10.
- Enable HDR in Windows when the display pipeline requires it.
- Set the monitor or television to an HDR-compatible mode.
- Verify that the capture path supports the selected format.
- Check whether P010 is appropriate for the 10-bit HDR workflow.
- Keep color-range settings consistent across the source, NitLink, GPU output, and display.
HDR controls image brightness and color information, while VRR controls refresh timing. They can work together, but each feature must be supported across the relevant hardware and software path.
Troubleshoot NitLink Setup Problems
When NitLink setup fails, isolate the problem in a fixed order: source signal, cable path, capture-card detection, application source selection, display format, and audio output. Avoid changing several settings at once because that can hide the original cause.
| Symptom | Likely checks | Recommended first action |
|---|---|---|
| Black screen | HDMI path, source power, selected input | Test a standard SDR signal and reselect the capture source |
| Capture card missing | USB or PCIe connection, device availability | Reconnect directly and close other capture applications |
| Washed-out HDR | Windows HDR, display mode, color range | Return to SDR, then retest HDR one setting at a time |
| Audio delay | Capture path, output device, buffering | Confirm the selected Windows playback device |
| Stretched picture | Aspect ratio and display scaling | Match NitLink output to the source aspect ratio |
| Tearing | VSync, refresh rate, Present Cap | Test synchronized output and compare with Low Latency mode |
| SmartScreen warning | Download origin and file integrity | Verify the official release source before launching |
Use the official NitLink FAQ for general support information and the NitLink GitHub Issues page for reproducible technical problems. A useful report should include the NitLink version, download source, capture-card model, console, resolution, refresh rate, display, and diagnostic Report ID when available.
Q: What does NitLink setup require?
You need a Windows PC, a DirectX 11-capable GPU, Microsoft WebView2, a Windows-recognized capture card, a console HDMI source, and a display. HDR and VRR require additional support from the source, capture card, GPU path, and monitor.
Q: Why does my capture card work in pass-through but not in NitLink?
Pass-through and Windows capture are separate parts of the signal path. Check the USB or PCIe connection, confirm that Windows lists the device, close other capture applications, and select the correct source in NitLink.
Q: Should I enable HDR immediately?
No. Establish a stable SDR image first. Then enable HDR in Windows and on the display, confirm the source is HDR10, and verify color range and pixel-format compatibility.
Q: How can I reduce delay in NitLink?
Enable Low Latency mode, use an appropriate display refresh rate, and evaluate VSync and Present Cap based on the source and display. Frame Generation may add latency, so it is better suited to situations where smoothness matters more than minimum response time.
If the basic checks do not resolve the issue, record the exact hardware chain and settings before opening a support report. Reproducible details help separate compatibility problems from configuration errors.