- NitLink requirements include a Windows PC, compatible capture card, active HDMI signal, and DirectX 11-capable GPU.
- WebView2 supports the application interface and should be available before the first launch.
- HDR10 and VRR require matching support across the console, capture path, Windows, GPU, and display.
- Low-latency settings should match the source frame rate, display refresh behavior, and tolerance for tearing.
- Official downloads are available through NitLink GitHub Releases and the official Steam listing.
NitLink Requirements at a Glance
NitLink is a Windows capture-card viewer designed to display a console signal in a PC window. Before installation, prepare the computer, capture hardware, HDMI path, and display features required for your intended setup. The most important NitLink requirements are a DirectX 11-capable GPU, Microsoft WebView2, a recognized capture device, and a display configured for the signal format you want to use.
Video Highlights:
- NitLink displays a PS5 signal in a Windows application window.
- The setup depends on a console, capture card, and PC display path.
- Windowed viewing can be used alongside other desktop applications.
- The walkthrough demonstrates the core purpose of the application.
| Requirement | Why It Matters | Preparation Check |
|---|---|---|
| Windows PC | Runs the NitLink application and presents the captured signal | Confirm the computer is ready before connecting the source |
| DirectX 11-capable GPU | Supports the rendering path used by the application | Verify the graphics hardware supports DirectX 11 |
| Microsoft WebView2 | Supports the application interface experience | Install or confirm WebView2 before launching |
| Capture card | Converts the console HDMI signal for Windows | Confirm that Windows can recognize the device |
| HDMI source path | Carries video from the console to the capture card | Connect the console output to the capture input |
| Compatible display | Shows the NitLink window and advanced formats | Use HDR or VRR hardware only when the complete path supports it |
Start with a standard SDR signal before testing HDR10, VRR, or high-refresh modes. This gives you a stable baseline for separating connection problems from advanced display-format problems.
NitLink is distributed through official channels, including the official GitHub repository, GitHub Releases, and the official Steam listing. The GitHub version is presented as a free, MIT-licensed capture-card viewer, while the Steam version provides an additional distribution option and includes experimental Frame Generation functionality.
Hardware and Windows Setup Requirements
The physical signal path should be ready before NitLink starts. Connect the console output to the capture card input, then connect the capture card to the Windows computer through its required USB or PCIe connection. A pass-through display can be added when you want the console signal available on a separate television or monitor.
Console Signal
- Connect the console HDMI output to the capture card input.
- Turn on the console before selecting the source in NitLink.
- Begin with a supported SDR resolution if testing a new setup.
Capture Hardware
- Use a compatible USB or PCIe capture device.
- Allow Windows time to initialize the device.
- Close other applications that may already be using the capture source.
Windows Environment
- Prepare a Windows PC with a DirectX 11-capable GPU.
- Confirm Microsoft WebView2 is available.
- Keep the application and capture device on an accessible setup path.
| Connection Stage | Correct Arrangement | Common Check |
|---|---|---|
| Console to capture card | Console HDMI output to capture HDMI input | Confirm the console is sending an active signal |
| Capture card to PC | USB or PCIe connection to Windows | Check that Windows recognizes the device |
| Optional pass-through | Capture card output to a television or monitor | Confirm pass-through supports the same display mode |
| NitLink source selection | Available capture source selected in the app | Select the correct device after launch |
Connect the Console
Connect the console HDMI output to the capture card HDMI input. Turn on the console and verify that its output is active. If the setup includes a pass-through display, connect it according to the capture card's instructions.
Connect the Capture Card to Windows
Attach the capture card through its required USB or PCIe connection. Give Windows time to initialize the device before launching NitLink. Avoid routing the device through an unstable connection while testing.
Confirm the Windows Environment
Check that the PC has a DirectX 11-capable GPU and Microsoft WebView2. These are important parts of NitLink's rendering and interface environment.
Launch NitLink
Open NitLink after the console and capture card are active. Select the available capture source, then confirm that the console image appears in the application window.
A capture card can be connected correctly and still fail to show an image if the selected resolution, refresh rate, HDR mode, or source format is unsupported. Test a basic signal before changing several settings at once.
HDR10, VRR, and Display Requirements
Advanced display features require coordination between the source, capture card, graphics output, Windows, and monitor. HDR10 affects brightness and color information, while VRR affects refresh timing. They are related to the viewing experience but should be tested as separate functions before combining them.
For HDR viewing, the source should provide HDR10, Windows HDR should be enabled when required by the display pipeline, and the monitor or television must operate in an HDR-compatible mode. A mismatch can produce gray blacks, washed-out colors, clipped highlights, or an image that appears incorrectly mapped.
| Feature | Required Conditions | Typical Symptom When Mismatched |
|---|---|---|
| HDR10 | HDR-capable source, capture path, Windows configuration, and display | Washed-out, gray, or overexposed image |
| P010 | Capture path, GPU, driver, and display support for a 10-bit workflow | Incorrect brightness or unavailable HDR output |
| Color range | Source, NitLink, graphics output, and display use consistent range interpretation | Crushed shadows, gray blacks, or clipped whites |
| VRR | Compatible display and graphics hardware with a supported refresh range | Tearing, unstable timing, or inconsistent motion |
| HDR plus VRR | Both feature chains work independently before being combined | Image problems combined with refresh instability |
To configure this efficiently:
- Confirm whether the source is SDR or HDR10.
- Enable HDR in Windows only when the display path is ready for HDR presentation.
- Check the monitor or television’s HDR mode.
- Keep limited-range and full-range settings consistent across the signal chain.
- Test VRR separately and keep the presented frame rate inside the display’s supported range.
- Use a Present Cap below the display’s maximum refresh rate when additional VRR headroom is needed.
HDR controls image format, while VRR controls display timing. When troubleshooting, test image quality first and variable refresh second. Combining both immediately can make the original problem harder to identify.
The NitLink FAQ is the preferred official reference for display-format checks. For reproducible compatibility problems, include the source device, capture card, display, resolution, refresh rate, and relevant NitLink settings when using the official GitHub issue tracker.
Performance and Low-Latency Requirements
NitLink performance depends on how captured frames are presented, synchronized, and paced on the display. The best configuration depends on the source frame rate and the display’s refresh behavior. Competitive games generally favor a shorter presentation path, while 30 FPS console games may benefit from steadier frame pacing.
| Use Case | Low Latency | VSync | Present Cap | Display Priority |
|---|---|---|---|---|
| Competitive games | Enabled | Disabled when tearing is acceptable | Uncapped or above source rate | Highest stable refresh rate |
| 30 FPS console games | Enabled | Enable when tearing is visible | 30 FPS or suitable multiple | Even frame pacing |
| VRR display | Enabled | Configure for the display behavior | Slightly below VRR maximum when needed | Stay inside VRR range |
| General viewing | Optional | Use when tearing is distracting | Match the source when practical | Stable, comfortable presentation |
Performance Readiness Checklist:
- Confirm the display refresh rate is set to a stable supported value
- Enable Low Latency when responsive presentation is the priority
- Use VSync only when its trade-off fits the display and source
- Match Present Cap to the source cadence or VRR range
- Test for tearing, uneven pacing, and additional delay after each change
The Steam version includes experimental Frame Generation, which uses the PC GPU to generate additional frames. It can support higher apparent output rates, such as converting a 30 FPS source toward a 60 FPS presentation, but it may add latency. Treat this function as an optional experiment rather than a requirement for basic NitLink viewing.
Use the simplest configuration that meets your goal. Start with Low Latency enabled, then adjust VSync and Present Cap according to visible tearing, frame pacing, VRR behavior, and perceived response.
NitLink can also support windowed viewing, full-screen presentation, picture-in-picture, screenshots, recording, and HUD controls. These features are useful for desktop multitasking, capture monitoring, and sharing the application window with tools such as OBS or Discord.
Troubleshooting NitLink Requirements
When NitLink does not display a signal, troubleshoot the chain in order rather than changing every setting simultaneously. Start with power and cables, then confirm Windows detection, source selection, resolution, refresh rate, and advanced formats.
| Problem | First Checks | Next Action |
|---|---|---|
| No signal or black screen | Reconnect cables, confirm source power, check capture-device detection | Select the correct source and test standard SDR |
| Capture card missing | Check USB or PCIe connection and close other capture applications | Restart NitLink and verify the device in Windows |
| HDR looks washed out | Check Windows HDR, display HDR mode, and color range | Test a supported 10-bit workflow such as P010 |
| Audio and video are out of sync | Check the selected audio path and processing | Compare low-latency and synchronized presentation modes |
| Picture is stretched | Check source resolution, aspect ratio, and display scaling | Use a matching aspect-ratio setting |
| SmartScreen warning | Verify the file came from an official NitLink channel | Recheck the release source and download integrity |
Follow this diagnostic order:
- Confirm the console is powered and producing a signal.
- Check the HDMI connection between the console and capture card.
- Confirm Windows recognizes the capture device.
- Close applications that may be using the capture card.
- Open NitLink and select the correct capture source.
- Test a standard SDR resolution before enabling HDR or VRR.
- Record the NitLink version, hardware, display, resolution, and settings if the issue continues.
When reporting a persistent issue, include the NitLink version, download source, capture-card model, console, Windows environment, resolution, display mode, and diagnostic Report ID when available.
For official support, use the NitLink FAQ, GitHub Issues, and Steam Discussions. NitLink’s official FAQ indicates that there is no official Discord currently, so these channels are the appropriate places to check updates and report reproducible problems.
Q: What are the minimum NitLink requirements for basic viewing?
You need a Windows PC, a DirectX 11-capable GPU, Microsoft WebView2, a compatible capture card, an active console HDMI signal, and a display for the NitLink window.
Q: Do I need HDR or VRR to use NitLink?
No. HDR10 and VRR are advanced display features, not basic requirements for viewing a standard captured signal. Start with SDR and add advanced features when the complete signal path supports them.
Q: Which capture cards work with NitLink?
Official materials identify support for devices including Elgato 4K Pro, 4K X, and 4K S, with support or verification also noted for Cam Link 4K and Game Capture 4K60 Pro MK.2. Confirm the current device status before purchase or setup.
Q: Can NitLink replace a direct HDMI connection for competitive play?
NitLink provides a convenient PC viewing path, but capture and presentation can introduce additional delay. For latency-sensitive play, compare the application output with a direct display path and use Low Latency settings.