- NitLink installation uses an official Windows release from GitHub or Steam.
- Hardware path: connect your console, capture card, Windows PC, and optional pass-through display.
- System needs: prepare a DirectX 11-capable GPU and Microsoft WebView2.
- First launch: select the capture source, confirm the image, then configure audio and display features.
- Troubleshooting: test standard SDR output before enabling HDR, VRR, or other advanced options.
NitLink Installation Sources and Requirements
NitLink installation is designed for Windows users who want to view a console signal through a compatible capture card. The official GitHub release is distributed as a Windows archive that can be extracted and launched directly, while the official Steam listing provides another supported distribution option.
Use the official GitHub Releases page for the portable release package. The official NitLink project page provides project information, while the Steam listing offers the store version. Avoid unofficial mirrors and republished executables.
| Installation option | Delivery method | Best for | Important note |
|---|---|---|---|
| GitHub release | Download and extract a Windows archive | Users who want the portable release | Launch NitLink.exe after extraction |
| Steam version | Install through the official Steam listing | Users who prefer library-based management | Includes the Steam distribution option and experimental Frame Generation |
| Unofficial mirror | Republished executable or archive | Not recommended | Source authenticity and file integrity are uncertain |
Official Windows Archive
Download the latest stable package from the official GitHub Releases page, then save it locally before extraction.
Portable Launch
The release package does not require a separate installer workflow. Extract the archive and run NitLink.exe.
Steam Distribution
The Steam listing provides a second official access route and keeps NitLink available in your Steam library.
Create a dedicated folder such as C:\Apps\NitLink before extracting the archive. Keeping the application in a stable location makes future updates and configuration checks easier.
| Requirement | Recommended preparation | Why it matters |
|---|---|---|
| Operating system | Supported Windows PC | NitLink is a Windows capture-card viewer |
| Graphics hardware | DirectX 11-capable GPU | Supports the rendering path used by the application |
| Web component | Microsoft WebView2 installed | Supports the application interface |
| Capture device | Compatible USB or PCIe capture card | Provides the console video signal |
| Display | Standard, HDR, or VRR-capable display as needed | Determines which viewing features can be tested |
Connect the Console and Capture Card
NitLink displays the signal supplied by your capture card, so the physical connection should be completed before the application starts. A basic setup uses the console HDMI output, the capture card HDMI input, and a USB or PCIe connection from the capture card to the Windows PC.
If your capture card has HDMI pass-through, connect its output to a television or monitor when you want to use a separate display. NitLink can then provide the Windows viewing window while the pass-through connection serves another screen.
Connect the Console HDMI Output
Connect the console HDMI output to the capture card HDMI input. Make sure the console is powered on and producing an active signal before selecting the source in NitLink.
Connect the Capture Card to Windows
Use the required USB connection for an external capture card or install the device in an available PCIe slot for an internal model. Wait for Windows to initialize the device.
Add an Optional Pass-Through Display
If the capture card supports HDMI pass-through, connect its output to a television or monitor. This is optional and is not required for viewing the signal in NitLink.
Prepare the Windows Display
Connect the display you want to use with NitLink. Enable Windows HDR only when you plan to test HDR content, and confirm VRR support before configuring variable refresh features.
Start NitLink After the Signal Is Ready
Open NitLink after the console and capture card are active. Select the available capture source and confirm that the console image appears in the application window.
| Connection point | Required action | Result |
|---|---|---|
| Console output | HDMI out to capture-card input | Sends the console signal to the capture device |
| Capture card | USB or PCIe connection to Windows | Makes the device available to the PC |
| Pass-through output | HDMI out to a separate display | Allows viewing on a television or monitor |
| Windows display | Connect and configure the target display | Provides the NitLink viewing surface |
Do not begin with every advanced feature enabled. First confirm a visible SDR image at a standard resolution, then test HDR, VRR, and higher refresh modes one at a time.
Complete the First NitLink Setup
After the physical connection is ready, the first launch should focus on confirming the capture source and establishing a stable viewing path. Keep the initial configuration simple. Window mode is useful during setup because it lets you monitor NitLink while changing Windows, audio, or display settings.
The application supports features such as windowed viewing, full screen, screenshots, picture-in-picture, audio output, HDR10, VRR, and low-latency presentation. These features may depend on the capture card, source signal, display, and graphics hardware.
Window Mode
Use a resizable window while testing the signal, adjusting settings, or placing the console feed beside chat, recording, or streaming software.
Picture-in-Picture
Keep the capture feed above other windows when monitoring the console while working in another application.
Full Screen
Expand the capture image for focused viewing after the signal and aspect ratio are confirmed.
| First-launch task | Recommended action | Success check |
|---|---|---|
| Select the source | Choose the available capture device | The console image appears |
| Confirm audio | Select the intended Windows playback device | Sound reaches speakers or headphones |
| Check aspect ratio | Match the source and display geometry | The image is not stretched |
| Test window controls | Resize or move the NitLink window | The feed remains visible and stable |
| Test advanced features | Enable HDR or VRR separately | The image remains correctly mapped |
Your initial setup is ready when NitLink shows the console image, audio reaches the intended output, and the picture keeps the correct aspect ratio in windowed mode.
HDR10 and VRR setup
HDR10 requires coordination between the console, capture path, Windows, graphics output, and display. Enable HDR in Windows and on the display when the complete chain supports HDR. If only one part of the chain is configured for HDR, the image may appear gray, washed out, or incorrectly exposed.
For a 10-bit HDR workflow, the provided configuration guidance identifies P010 as a relevant pixel format. Test it only after confirming that the capture device, graphics driver, and display support the selected format.
VRR is a timing feature rather than an image-format feature. G-Sync and FreeSync-compatible displays may require a suitable refresh range and a Present Cap below the monitor's maximum refresh rate. Test HDR and VRR separately before combining them.
Choose a Stable Performance Configuration
NitLink performance settings should match the source frame rate, display refresh rate, and desired balance between responsiveness and frame pacing. A low-latency configuration can be useful for responsive play, while synchronized presentation may look steadier for 30 FPS console content.
The Steam version also includes experimental Frame Generation. This feature uses the PC GPU to create additional frames, but it may introduce extra latency. Treat it as an optional performance experiment rather than a default requirement for every setup.
| Use case | Low Latency | VSync | Present Cap | Practical priority |
|---|---|---|---|---|
| Responsive gameplay | Enabled | Disabled when tearing is acceptable | Uncapped or above source rate | Minimize presentation delay |
| 30 FPS content | Enabled | Enable if tearing appears | 30 FPS or a suitable multiple | Keep frame pacing even |
| VRR display | Enabled | Match the display behavior | Slightly below VRR maximum when needed | Stay inside the VRR range |
| Experimental Frame Generation | Test carefully | Depends on the display path | Match the intended output | Compare smoothness against added latency |
Configuration and hotkeys
Use runtime controls for quick changes to Low Latency, VSync, HDR, picture-in-picture, aspect ratio, and HUD visibility. Use nitlink.json when you need repeatable settings for display pacing, refresh-rate limits, Present Cap, or audio behavior.
Change one performance setting at a time and compare the result with the previous configuration. This makes it easier to identify whether a problem comes from timing, HDR, VRR, or the capture signal itself.
Installation and First-Run Checklist:
- Download NitLink from the official GitHub Releases page or Steam listing
- Extract the Windows archive and launch NitLink.exe when using the portable release
- Connect the console, capture card, and Windows PC
- Confirm the capture source and visible console image
- Test audio, aspect ratio, HDR, and VRR separately
Troubleshoot NitLink Installation Problems
Most setup problems can be narrowed down by checking the signal path, Windows device detection, source selection, display format, and audio route in that order. Start with a standard SDR signal before investigating HDR or VRR behavior.
| Problem | Likely cause | First checks |
|---|---|---|
| Black screen | Inactive source, wrong input, or unsupported mode | Reconnect HDMI, confirm Windows detection, select the correct source |
| Capture card missing | Device unavailable or used by another app | Close other capture software and reconnect the device |
| HDR looks washed out | Windows, display, or color-range mismatch | Confirm HDR state, source type, and color-range settings |
| Audio is delayed | Different buffering in the capture path | Check the selected output and compare presentation modes |
| Image is stretched | Aspect-ratio or scaling mismatch | Match source resolution and disable forced display stretching |
| SmartScreen warning | New or unfamiliar downloaded release | Verify the official source and review the file before launching |
When reporting a persistent issue through the NitLink GitHub Issues page, include the application version, download source, capture-card model, console, resolution, display, and diagnostic Report ID when available. The official NitLink FAQ is also useful for checking common display and support questions.
Do not change several variables at once. Test the cable path, capture-device visibility, source selection, standard SDR output, audio, and advanced display features in sequence.
Q: What is the simplest NitLink installation method?
Download the latest Windows archive from the official GitHub Releases page, extract it to a stable folder, and launch NitLink.exe. Connect the console and capture card before selecting the source.
Q: Does NitLink require a separate installer?
The portable GitHub release does not require a separate installer workflow. Extract the archive and run NitLink.exe. Steam provides a separate official distribution option.
Q: Why does NitLink show a black screen?
Check the HDMI path, confirm that Windows recognizes the capture card, close other applications using the device, and select the correct capture source. Test a standard SDR signal before HDR.
Q: Can I use HDR and VRR during setup?
Yes, when the console, capture card, Windows display path, graphics hardware, and monitor support them. Establish a stable SDR image first, then test HDR and VRR separately.