- NitLink how to use starts with connecting your console to a compatible capture card.
- Windows setup requires a recognized capture device, a DirectX 11-capable GPU, and WebView2.
- First launch is complete when NitLink detects the source and displays the console image.
- Low latency depends on VSync, refresh rate, Present Cap, and the display’s timing behavior.
- HDR and VRR should be configured across the source, Windows, NitLink, and the display.
NitLink How to Use: What You Need
NitLink is a Windows capture-card viewer that displays a console signal in a PC window. The simplest workflow is to connect the console to a capture card, connect that device to Windows, and select the available source in NitLink. You can then use window mode, full screen, audio output, screenshots, picture-in-picture, HDR, VRR, and performance controls according to your hardware.
Before opening the application, prepare the complete signal path. A missing HDMI connection, unsupported display mode, or capture card being used by another application can prevent the first image from appearing.
Console Signal
Connect the console HDMI output to the capture card input. Turn on the console before testing the source in NitLink.
Windows PC
Use a Windows computer with a DirectX 11-capable GPU and Microsoft WebView2 available for the application interface and rendering path.
Display Setup
Use an HDR-capable display for HDR viewing or a VRR-capable display for variable-refresh features. Enable supported modes in Windows.
| Requirement | What to check | Why it matters |
|---|---|---|
| Console | HDMI output is active | NitLink needs an incoming source signal |
| Capture card | USB or PCIe device is powered and connected | Windows must expose the device as an available capture source |
| Windows PC | DirectX 11-capable GPU | Supports the application’s rendering path |
| WebView2 | Microsoft WebView2 is installed | Supports the NitLink interface experience |
| Display | HDR or VRR capability when needed | Required for the matching advanced display feature |
Begin with a standard SDR signal at a familiar resolution. Confirm that video works before enabling HDR, VRR, or experimental frame generation.
Official downloads should come from the NitLink GitHub Releases page or the official Steam listing. Avoid modified packages and unofficial mirrors.
NitLink Windows Setup: Step-by-Step
The most reliable setup order is to prepare the hardware first, allow Windows to initialize the capture device, and launch NitLink only after the source is active. This reduces confusion when multiple video devices or display modes are present.
Connect the Console to the Capture Card
Connect the console HDMI output to the capture card HDMI input. If the capture card has HDMI pass-through, connect its output to a television or monitor when you want to use a separate display. Turn on the console and confirm that it is producing an active signal.
Connect the Capture Card to Windows
Connect the capture card through its required USB or PCIe connection. Give Windows time to initialize the device. Close other software that may already be using the capture card, including streaming, recording, or camera applications.
Prepare Windows and the Display
Confirm that the Windows computer meets the basic requirements. For HDR or VRR, enable the matching feature in Windows and on the connected monitor or television before testing the signal in NitLink.
Open NitLink and Select the Source
Launch NitLink after the console and capture card are active. Select the available capture source, then check whether the console image appears. If more than one video device is listed, verify the selected model and input.
Choose a Viewing Mode
Start in window mode while checking video, audio, and display settings. Resize the window, move it to another monitor, or switch to full screen after the basic signal is stable. Picture-in-picture can keep the console feed visible while you use other desktop applications.
| Setup stage | Successful result | If it fails |
|---|---|---|
| HDMI connection | Console signal reaches the capture card | Reseat both HDMI ends and test the console output |
| Device connection | Windows recognizes the capture card | Reconnect directly and close software using the device |
| Source selection | NitLink lists the correct capture input | Check Windows video-device availability |
| Initial display | Console image appears in the window | Test SDR before HDR or advanced timing modes |
| Viewing mode | Window, full screen, or picture-in-picture works | Return to window mode and review display settings |
Your initial setup is ready when NitLink displays a stable console image and Windows shows the capture card as an available video device.
NitLink Video, Audio, HDR, and VRR Controls
Once the video feed works, adjust one feature at a time. NitLink can be used as a basic viewer, a flexible desktop window, or a more advanced display path with HDR, VRR, low-latency presentation, and picture-in-picture.
Everyday viewing controls
Window mode is useful while configuring the application or monitoring another program. Full screen gives the captured image more display space, while picture-in-picture keeps the source visible above other desktop windows. Screenshots can save a still image from the current feed for sharing or documenting a setup.
Choose the audio output that matches your listening device. If you use headphones, connect them before selecting the Windows playback device and verify that the system volume is active.
HDR configuration
HDR requires agreement between the source, capture path, Windows, NitLink, graphics hardware, and display. Enable HDR in Windows when the application is expected to present HDR content through the Windows display pipeline. The monitor or television must also be operating in an HDR-compatible mode.
P010 may be appropriate for a 10-bit HDR workflow when the capture path, graphics driver, and display support it. If the image appears gray, washed out, or overexposed, check the source format, Windows HDR state, display mode, pixel format, and color range.
VRR configuration
VRR changes display timing rather than image color. A compatible monitor and graphics path are required, and the presented frame rate should remain inside the display’s supported VRR range. G-Sync and FreeSync behavior can vary by hardware and driver configuration.
| Feature | Main purpose | Key checks |
|---|---|---|
| Window mode | Desktop multitasking and configuration | Resize, reposition, and test the source |
| Full screen | Focused viewing | Confirm the display resolution and refresh rate |
| Picture-in-picture | Floating console view | Check placement, size, and other window visibility |
| HDR10 | High-dynamic-range presentation | Match Windows, source, pixel format, and display |
| VRR | Variable-refresh timing | Keep output within the monitor’s supported range |
| P010 | 10-bit HDR format | Confirm support across the complete signal path |
Do not troubleshoot HDR and VRR at the same time initially. Test SDR first, then HDR, then VRR so each change has a clear result.
Low-Latency Settings and Performance Tips
NitLink’s performance settings should match the source frame rate and the behavior of the display. The lowest possible latency is not always the smoothest choice for a 30 FPS source or a VRR monitor. Adjust presentation behavior based on whether responsiveness, frame pacing, or tear reduction is the priority.
Competitive Viewing
Enable Low Latency, consider disabling VSync, and use the highest stable display refresh rate available. Avoid unnecessary frame caps when immediate response is the priority.
30 FPS Sources
Prioritize even frame pacing. A Present Cap aligned with the source cadence can make camera movement appear more consistent.
VRR Displays
Enable VRR across the supported chain and keep presentation below the display’s maximum when additional headroom is useful.
| Scenario | Low Latency | VSync | Present Cap | Priority |
|---|---|---|---|---|
| Competitive games | Enabled | Disabled when tearing is acceptable | Uncapped or above source rate | Minimum display delay |
| 30 FPS console games | Enabled | Enable if tearing appears | 30 FPS or suitable multiple | Stable frame pacing |
| VRR display | Enabled | Match the VRR workflow | Slightly below VRR maximum when needed | Smooth variable refresh |
| Mixed desktop use | Test both modes | Enable if tearing distracts | Match the chosen display behavior | Balanced viewing |
How to use Present Cap
Present Cap limits how frequently NitLink presents frames. Use it to match a stable source cadence, reduce unnecessary queueing, or stay inside a VRR operating range. Change the cap gradually and observe motion, tearing, and responsiveness after each adjustment.
Experimental frame generation is available through the Steam version. It can generate additional frames with the PC GPU, but it may add latency. This makes it better suited to visual smoothness experiments than latency-sensitive competitive play.
Before You Start Playing:
- Console HDMI output is connected to the capture card input
- Windows recognizes the capture card and no other application is using it
- NitLink displays the correct source in window mode
- Audio output is routed to the intended speakers or headphones
- HDR, VRR, VSync, and Present Cap match the selected display setup
Change one setting at a time and test a familiar scene. This makes it easier to identify whether latency, tearing, or pacing improved.
NitLink Troubleshooting and FAQ
Most problems can be narrowed down by checking the signal path, device selection, display format, and Windows state in that order. Before reporting a persistent issue, record the NitLink version, download source, capture-card model, console, display, resolution, and diagnostic Report ID when available. Use the NitLink FAQ or GitHub Issues for official support routes.
| Problem | Likely cause | Recommended first check |
|---|---|---|
| Black screen | No active source or unsupported signal mode | Reconnect HDMI and test standard SDR |
| Capture card missing | Windows has not initialized the device | Reconnect directly and close other capture software |
| Washed-out HDR | HDR or color-range mismatch | Check Windows HDR, display HDR, and source range |
| Audio delay | Different buffering in the capture path | Compare low-latency and synchronized settings |
| Stretched image | Aspect-ratio or scaling mismatch | Match source resolution and disable forced display stretch |
| SmartScreen warning | New or infrequently downloaded release | Verify the official download origin before launching |
Q: How do I use NitLink for the first time?
Connect the console to the capture card, connect the capture card to Windows, launch NitLink, select the available source, and confirm that the console image appears in the window.
Q: Why does NitLink show a black screen?
Check the HDMI path, console output, capture-card power, Windows device recognition, and selected input. If advanced modes are enabled, test a standard SDR resolution before HDR or VRR.
Q: Can I use HDR and VRR together in NitLink?
They can work together when the source, capture path, graphics hardware, Windows, and display support both features. Test HDR and VRR separately first, then combine them.
Q: Which NitLink settings reduce display delay?
Low Latency mode is the main starting point. VSync, refresh rate, and Present Cap also affect behavior, so choose settings that match the source cadence and display.
When opening a report, include the application version, download source, capture card, console, Windows display mode, resolution, and any available Report ID.