NitLink setup: Step-by-Step Windows Capture Guide - Guide

NitLink setup: Step-by-Step Windows Capture Guide

Follow this NitLink setup guide to connect a console, configure a capture card, prepare Windows, and tune HDR, VRR, audio, and latency.

2026-11-19
NitLink Wiki Team
Quick Guide
  • 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.

ComponentBasic requirementSetup purpose
Windows PCWindows system with a compatible GPURuns NitLink and presents the captured image
Graphics hardwareDirectX 11-capable GPUSupports rendering and display output
Capture cardWindows-recognized USB or PCIe deviceReceives the console video signal
ConsoleHDMI video outputProvides the source image and audio
DisplayStandard monitor; HDR or VRR model for advanced featuresShows the NitLink window
SoftwareNitLink release and WebView2Provides 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.

Preparation Tip

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 stageCable or portWhat to confirm
Console to capture cardConsole HDMI output to capture inputThe input receives an active signal
Capture card to WindowsUSB or installed PCIe connectionWindows recognizes the device
Optional pass-throughCapture output to television or monitorThe display supports the same signal mode
Windows to monitorGPU output to displayThe NitLink window has a usable destination
Audio pathHDMI audio through the capture deviceAudio is available to the selected output
1

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.

2

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.

3

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.

4

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.

5

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.

Connection Warning

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.

DistributionTypical workflowBest use
GitHub ReleasesDownload the Windows archive, extract it, launch NitLink.exePortable official release
Steam listingInstall through the official Steam pageStore-based installation and library access
Unofficial mirrorAvoidFile authenticity and update status are uncertain
  1. Open the official NitLink GitHub Releases page.
  2. Select the current Windows release asset.
  3. Save the archive to a local folder.
  4. Extract the archive to a location you can access easily.
  5. Launch NitLink.exe.
  6. If Windows shows a security prompt, verify that the file came from the official release channel before proceeding.
  7. Select the available capture source inside NitLink.
  8. 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
Launch Check

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.

GoalRecommended starting pointWhat to watch
Basic viewingWindow mode, SDR, standard refresh rateStable image and correct aspect ratio
Low latencyLow Latency enabled, appropriate VSync settingResponsiveness versus tearing
30 FPS sourceMatched Present Cap and even frame pacingUneven motion or repeated frames
HDR viewingWindows HDR enabled with HDR display modeGray blacks, washed highlights, wrong colors
VRR viewingCompatible display with output inside VRR rangeFlicker, tearing, or unstable refresh
MultitaskingPicture-in-pictureWindow position and visibility
Focused playFull screenScaling 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 and VRR Note

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.

SymptomLikely checksRecommended first action
Black screenHDMI path, source power, selected inputTest a standard SDR signal and reselect the capture source
Capture card missingUSB or PCIe connection, device availabilityReconnect directly and close other capture applications
Washed-out HDRWindows HDR, display mode, color rangeReturn to SDR, then retest HDR one setting at a time
Audio delayCapture path, output device, bufferingConfirm the selected Windows playback device
Stretched pictureAspect ratio and display scalingMatch NitLink output to the source aspect ratio
TearingVSync, refresh rate, Present CapTest synchronized output and compare with Low Latency mode
SmartScreen warningDownload origin and file integrityVerify 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.

Reporting Tip

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.

Keep Reading