- NitLink capture card viewing runs through the Windows application and a compatible video input device.
- Official downloads are available through GitHub Releases and the official Steam listing.
- Best first test: use a standard SDR signal before enabling HDR10, VRR, or frame generation.
- Low-latency setup depends on VSync, Present Cap, display refresh rate, and the source frame rate.
- Troubleshooting starts with cables, Windows device detection, source selection, and signal format.
NitLink Capture Card Basics and First Launch
NitLink is a Windows capture-card viewer designed to display a console signal in a PC window. It supports features such as HDR10 presentation, VRR workflows, picture-in-picture, screenshots, recording, low-latency display, and an experimental frame-generation mode in the Steam version.
The application is useful when you want to view a console through your PC, monitor the signal beside other Windows applications, or use the feed with tools such as OBS and Discord. It does not replace the capture card itself: the console still needs to send an HDMI signal through compatible capture hardware.
Video Highlights:
- Connecting a console signal to NitLink on a Windows PC
- Viewing a PlayStation 5 feed inside a desktop window
- Understanding the basic capture-card viewing workflow
| Component | Role in the setup | Key check |
|---|---|---|
| Console | Provides the HDMI video and audio signal | Console is powered on and outputting an active signal |
| Capture card | Converts the HDMI signal for Windows | Device is connected and visible to Windows |
| Windows PC | Runs NitLink and presents the captured image | DirectX 11-capable GPU and WebView2 are available |
| Display | Shows the NitLink window | HDR or VRR capability matches the intended feature |
| Optional pass-through display | Shows the console directly while NitLink runs | Capture card supports the desired pass-through mode |
NitLink is distributed through official channels. The GitHub version is presented as a free, MIT-licensed viewer, while the Steam version provides an additional distribution option and experimental frame generation. Use the official GitHub Releases page or the NitLink Steam listing rather than modified mirrors.
Start with a standard SDR resolution and refresh rate. Confirm that the image and audio work before changing HDR, VRR, or frame-presentation settings.
Step-by-Step NitLink Capture Card Setup
Follow this sequence when configuring NitLink for the first time. The order matters because it separates physical connection problems from Windows, display, and application settings.
Connect the Console to the Capture Card
Connect the console HDMI output to the capture card HDMI input. If the card includes HDMI pass-through, connect its output to a television or monitor when you want to play directly on another display. Turn on the console before selecting the source in NitLink.
Connect the Capture Card to Windows
Connect a USB capture card to the Windows PC using the required cable and port. For an internal PCIe device, confirm that the card is installed correctly and that Windows has had time to initialize it. Close other applications that may already be using the capture source.
Prepare the Windows Environment
Use a Windows system with a DirectX 11-capable GPU. Microsoft WebView2 should also be available because NitLink uses it for its application interface. Keep Windows and graphics drivers current enough to support the selected display workflow.
Prepare the Display
For HDR viewing, use an HDR-capable monitor or television and enable HDR in Windows when appropriate. For VRR, use a compatible display and graphics path. Begin with normal SDR output if you are diagnosing a new setup.
Launch NitLink and Select the Source
Start NitLink after the console and capture card are active. Select the available capture source, confirm that the console image appears, and then choose windowed, full-screen, or picture-in-picture viewing.
| Setup stage | What to confirm | Expected result |
|---|---|---|
| HDMI input | Console output reaches the capture card input | Capture hardware receives an active signal |
| USB or PCIe link | Capture card is connected to the PC | Windows detects the video device |
| Application source | Correct capture input is selected | Console image appears in NitLink |
| Audio route | Intended Windows playback device is selected | Console audio reaches speakers or headphones |
| Display mode | Window, full screen, or picture-in-picture is selected | Image fits the intended desktop workflow |
A basic setup is ready when NitLink displays the console image, Windows detects the capture device, and audio plays through the selected output. Test advanced features only after reaching this point.
Capture Card Compatibility and Feature Planning
NitLink compatibility depends on more than the brand name printed on a capture card. The device must expose a usable video source to Windows, and its input format must match the console, display, and intended feature set.
The official project information highlights Elgato 4K Pro, Elgato 4K X, and Elgato 4K S among its important supported devices. It also references Cam Link 4K and Game Capture 4K60 Pro MK.2 as supported or tested hardware. Exact behavior can still vary by resolution, HDR mode, refresh rate, drivers, and connection type.
USB Capture Cards
- Portable and easy to move between systems
- Confirm Windows device detection
- Check USB bandwidth and input limits
PCIe Capture Cards
- Suited to a permanent desktop setup
- Check installation and driver visibility
- Useful for high-bandwidth capture workflows
4K and HDR Devices
- Better suited to high-resolution console signals
- HDR support remains model-dependent
- Verify pixel format and color-range behavior
| Capture card or category | Connection | NitLink planning notes |
|---|---|---|
| Elgato 4K Pro | PCIe | Confirm installation, Windows visibility, and desired 4K or HDR mode |
| Elgato 4K X | USB | Check USB connection, input format, and high-resolution signal support |
| Elgato 4K S | USB | Verify available capture source and display format |
| Cam Link 4K | USB | Confirm the source appears as a Windows video device |
| Game Capture 4K60 Pro MK.2 | PCIe | Check driver state, input resolution, and HDR behavior |
| Unlisted device | USB or PCIe | Test standard SDR first and report reproducible results through official support channels |
Use the NitLink GitHub issue tracker when a device is not detected or behaves differently from expectations. Include the capture-card model, Windows version, console, resolution, refresh rate, HDR state, and diagnostic Report ID when available.
A capture card may support a signal on paper but still fail in a specific chain. Test the console, capture device, Windows format, and display together instead of assuming that one specification guarantees compatibility.
HDR10, VRR, and Low-Latency Settings
NitLink has separate display and timing concerns. HDR10 controls image brightness and color information, while VRR changes how the display refreshes. Low-latency settings control presentation behavior and can involve tradeoffs between responsiveness, tearing, and frame pacing.
For a first pass, keep the source and display simple. Enable HDR only when the console, capture card, Windows configuration, graphics hardware, and monitor all support the same HDR path. For VRR, keep the presented frame rate inside the monitor’s supported range.
| Use case | Low Latency | VSync | Present Cap | Recommended focus |
|---|---|---|---|---|
| Competitive games | Enabled | Disabled when tearing is acceptable | Uncapped or above source rate | Minimize presentation delay |
| 30 FPS console games | Enabled | Enable if tearing appears | Around 30 FPS or a suitable multiple | Keep frame pacing even |
| VRR display | Enabled | Match the display workflow | Slightly below VRR maximum when needed | Preserve VRR headroom |
| HDR viewing | Based on latency priority | Based on tearing and pacing | Match source or display needs | Keep format and color range consistent |
HDR10 configuration
Check these items in order:
- Confirm whether the console is sending SDR or HDR10.
- Enable Windows HDR when the NitLink presentation path requires it.
- Confirm that the monitor or television is in an HDR-compatible mode.
- Use a suitable 10-bit format such as P010 when required by the workflow.
- Match limited-range or full-range interpretation across the source, application, graphics output, and display.
VRR configuration
VRR works best when the output stays inside the display’s supported refresh range. G-Sync and FreeSync behavior also depends on the monitor, graphics hardware, driver configuration, and connection path. If the frame rate repeatedly reaches the display’s upper limit, a Present Cap below that limit may provide more consistent behavior.
The Steam version includes experimental frame generation. This feature uses the PC GPU to create additional frames, such as converting a 30 FPS source toward a higher presentation rate. It can add latency, so it is better suited to scenarios where smoothness matters more than the shortest possible response.
Change the source format, HDR state, VSync, Present Cap, or frame generation setting separately. This makes it easier to identify which change caused a visual, timing, or latency difference.
Troubleshooting and Verification Checklist
Most NitLink problems can be narrowed down by checking the signal path in a fixed order. Start with the console and cables, then move to Windows detection, source selection, display format, audio, and advanced timing settings.
Before Reporting a Problem:
- Confirm the console is powered on and sending an active HDMI signal
- Reconnect the capture card and verify that Windows detects it
- Close other applications that may be using the capture device
- Test a standard SDR resolution before enabling HDR or VRR
- Record the NitLink version, hardware models, display mode, and diagnostic Report ID
| Problem | Likely causes | First checks |
|---|---|---|
| Black screen or no signal | Wrong input, inactive source, unsupported format | Reconnect HDMI, select the correct source, test standard SDR |
| Capture card not detected | Cable, driver, USB or PCIe issue, another app using device | Check Windows devices, close capture software, restart NitLink |
| Washed-out HDR | Windows HDR mismatch, color-range mismatch, unsupported format | Check HDR state, range, display mode, and P010 support |
| Audio delay | Capture buffering, output-device processing, timing changes | Confirm audio route, compare presentation modes, restart after changes |
| Stretched image | Aspect-ratio mismatch or forced display scaling | Match source ratio, check NitLink scaling, disable display zoom |
| SmartScreen warning | New or less frequently downloaded release | Confirm official download source and inspect the file origin |
When reporting a persistent issue, provide enough detail for the maintainers to reproduce it. The most useful report includes the NitLink version, download source, Windows version, capture-card model, console, display, resolution, refresh rate, HDR or VRR state, and Report ID.
Test the same capture card with a basic SDR signal, one display, and no other capture application running. Add HDR, VRR, OBS, Discord, or frame generation only after the basic path works.
Official support paths
Use the NitLink FAQ for common setup and display questions, the GitHub Issues page for reproducible technical problems, and Steam Discussions for questions related to the Steam distribution.
Q: What does a NitLink capture card setup require?
You need a console with an active HDMI output, a compatible USB or PCIe capture card, a Windows PC, and a display. NitLink also expects a DirectX 11-capable GPU, with WebView2 available for the application interface.
Q: Can NitLink display HDR10 and VRR at the same time?
They can work together when the console, capture card, Windows configuration, graphics hardware, and display all support the required signal and timing path. Test HDR and VRR separately first, then combine them.
Q: Why is my capture card detected but the NitLink window is black?
Check the console signal, HDMI input, selected NitLink source, resolution, refresh rate, and HDR mode. A standard SDR test can help identify whether the advanced format is causing the problem.
Q: Does NitLink frame generation remove input lag?
No. Frame generation can make motion appear smoother by creating additional frames, but the Steam version describes it as experimental and notes that it can add latency. Use it selectively rather than treating it as a latency-reduction feature.