- NitLink resolution error usually requires checking the HDMI signal, capture source, and display mode.
- Start with SDR at a standard resolution before testing HDR, VRR, or high-refresh modes.
- Match the signal chain across the console, capture card, NitLink, Windows, and display.
- Check scaling settings when the image is stretched, cropped, or shown with the wrong aspect ratio.
- Report persistent issues with your version, hardware, resolution, and diagnostic details.
NitLink Resolution Error: What It Usually Means
A NitLink resolution error can appear as a black screen, no signal, an unsupported display mode, a stretched picture, or a capture feed that never becomes visible. The problem is usually caused by a mismatch somewhere between the console output, HDMI path, capture card, Windows video device, NitLink settings, and monitor.
NitLink is a Windows capture card viewer rather than a direct HDMI display connection. That means the captured signal must be recognized by Windows and presented through a compatible format before it can appear correctly in the application. Begin with a simple SDR signal, confirm the image, and then re-enable advanced features one at a time.
| Symptom | Likely area | First check |
|---|---|---|
| Black screen or no signal | HDMI path or source mode | Reconnect cables and test a standard SDR signal |
| Capture device missing | Windows or another application | Check whether Windows lists the capture card |
| Stretched image | Aspect ratio or scaling | Match the source and NitLink aspect-ratio settings |
| Washed-out HDR image | HDR or color-range mismatch | Compare Windows HDR, display HDR, and source settings |
| Tearing or uneven motion | VSync, VRR, or Present Cap | Test synchronized timing before changing advanced options |
Signal First
Confirm that the console is outputting an active HDMI signal and that the capture card is connected to the correct input.
Format Second
Test a standard SDR resolution and refresh rate before enabling HDR10, P010, VRR, or unusual refresh modes.
Display Last
After the capture feed appears, adjust scaling, aspect ratio, HDR, and refresh behavior for the target monitor.
Use the simplest supported signal path first: console to capture card, capture card to Windows, and NitLink displaying a standard SDR feed. Advanced settings are easier to diagnose after the basic image works.
Check the Complete Signal Chain
Resolution troubleshooting is most effective when you inspect each connection in order. A capture card can be powered and visible to Windows while still receiving an unsupported HDMI mode. Similarly, a console may show a picture on a television while the capture input rejects the selected resolution, HDR state, or refresh rate.
Follow the physical path from the source to the application. If the console uses an HDMI switch, receiver, splitter, or other intermediate device, temporarily remove unnecessary equipment while testing. For a pass-through setup, confirm that the capture card supports the same mode on both its HDMI input and output.
| Signal stage | What to verify | Useful test |
|---|---|---|
| Console output | Active HDMI output and supported resolution | Select a standard SDR mode |
| HDMI cable | Secure connection and suitable bandwidth | Replace the cable temporarily |
| Capture input | Correct HDMI input and device power | Reconnect the capture card |
| Windows device | Capture card appears as an available video device | Check Windows device lists |
| NitLink source | Correct capture source selected | Restart NitLink after reconnecting |
| Display output | Monitor mode matches the presented signal | Test a native display mode |
Power and Connect the Source
Turn on the console and connect its HDMI output to the capture card input. If you use pass-through, connect the capture card output to the television or monitor. Confirm that every connector is fully seated.
Connect the Capture Card to Windows
Attach the capture card through its required USB or PCIe connection. Wait for Windows to initialize it before opening NitLink. Avoid testing through an unreliable hub when a direct connection is available.
Close Conflicting Applications
Exit OBS, video-call software, browser capture tools, and other applications that may already be using the capture device. Reopen NitLink after the device is available.
Select the Correct Capture Source
Start NitLink and choose the available capture input. If several video devices are listed, test each relevant source rather than assuming the first entry is correct.
Confirm a Visible Frame
Wait for the console image to appear before changing HDR, VRR, VSync, or frame-presentation settings. If the feed remains blank, return to the physical connection and Windows detection checks.
Do not enable HDR, VRR, high refresh rates, and custom scaling simultaneously during the first test. One change at a time makes the failing part of the signal chain easier to identify.
Match Resolution, Refresh Rate, and HDR
Once NitLink recognizes the capture source, match the source signal to the capabilities of the capture card and display. Resolution is only one part of the mode. Refresh rate, HDR state, pixel format, and color range can also determine whether the image is accepted or displayed correctly.
A reliable sequence is to test SDR first, then HDR, and finally VRR or other timing features. If a mode fails, return to the last working configuration and change only one setting.
| Test profile | Recommended purpose | Settings to verify |
|---|---|---|
| Standard SDR | Establish a baseline | Common resolution, stable refresh rate, HDR disabled |
| HDR10 | Test high-dynamic-range presentation | Windows HDR, display HDR, source HDR, compatible capture path |
| P010 workflow | Test 10-bit HDR handling | Capture support, graphics driver, display format |
| VRR display | Test variable refresh | Supported VRR range, refresh ceiling, Present Cap |
| High refresh mode | Test faster presentation | Capture-card input limit and display refresh support |
When HDR appears gray, washed out, or overexposed, check the complete HDR workflow instead of changing brightness immediately. Windows HDR, the monitor or television HDR mode, the source output, and NitLink’s selected format must agree. A limited-range and full-range mismatch can also cause gray blacks, crushed shadows, or clipped highlights.
VRR is a timing feature, not a replacement for correct image formatting. Test the image without VRR first. Then enable variable refresh and keep the presented frame rate inside the display’s supported range. A Present Cap below the display’s maximum refresh rate may help maintain VRR headroom, depending on the monitor and configuration.
| Setting | If the image fails | Safer diagnostic action |
|---|---|---|
| Resolution | No signal or unsupported mode | Return to a standard SDR resolution |
| Refresh rate | Black screen or unstable image | Test a lower, stable refresh rate |
| HDR | Gray or overexposed picture | Disable HDR, then verify each HDR stage |
| Pixel format | Incorrect color or no image | Test the supported default format |
| Color range | Gray blacks or clipped whites | Match range across source and display |
| VRR | Flicker or uneven timing | Disable VRR and retest the baseline |
HDR controls color and brightness information, while VRR controls refresh timing. Test them independently before combining both features in the same NitLink setup.
Fix Scaling, Aspect Ratio, and Presentation Problems
A resolution problem does not always produce a black screen. NitLink may display the source while applying the wrong geometry, making the image appear stretched, cropped, or surrounded by unexpected borders. These symptoms usually point to scaling or aspect-ratio settings rather than a failed HDMI connection.
Begin by comparing the source resolution with the NitLink window and the monitor’s native aspect ratio. Disable forced zoom or stretch modes on the display while testing. If the source uses a format different from the monitor, preserve the original ratio before experimenting with fill or crop behavior.
| Visual issue | Common cause | Recommended adjustment |
|---|---|---|
| Wide or distorted image | Forced stretch | Preserve the source aspect ratio |
| Cropped edges | Overscan or zoom | Disable display zoom and check NitLink scaling |
| Large borders | Mismatched aspect ratio | Test a matching window or display mode |
| Uneven motion | Frame pacing mismatch | Align Present Cap with source cadence |
| Visible tearing | Unsynchronized presentation | Test VSync or compatible VRR behavior |
Resolution Error Checklist:
- Confirm the console is outputting an active HDMI signal
- Check that Windows recognizes the capture card
- Close other applications using the capture device
- Test a standard SDR resolution before HDR or VRR
- Match the source aspect ratio and display scaling
- Restart NitLink after changing the capture device
For low-latency setups, disabling VSync may reduce presentation delay but can expose tearing. For 30 FPS console content, synchronized timing and a suitable Present Cap may produce more even motion than an uncapped configuration. For VRR displays, keep the output within the supported operating range rather than forcing the highest possible refresh rate.
After you find a stable resolution, save or note the working source, refresh rate, HDR state, color range, and scaling behavior. This gives you a dependable baseline for future changes.
When to Report a NitLink Resolution Issue
If the capture feed still fails after cable, source, Windows, and format checks, prepare a clear support report. The official FAQ recommends including the NitLink version, download source, capture card, console, resolution, and diagnostic Report ID when available.
Use the NitLink FAQ for official troubleshooting guidance, the GitHub Issues tracker for reproducible problems, and the official GitHub Releases page to verify the release being used.
| Report detail | Example information to provide |
|---|---|
| NitLink version | Installed or extracted release version |
| Download source | Official GitHub release or Steam listing |
| Windows environment | Windows version and relevant display setup |
| Console | PS5, Xbox, Nintendo Switch, or another source |
| Capture hardware | Brand, model, USB or PCIe connection |
| Signal mode | Resolution, refresh rate, SDR or HDR |
| Display | Monitor or television model and VRR capability |
| Reproduction steps | What was changed before the error appeared |
| Diagnostic data | Report ID or relevant screenshots, if available |
Before opening an issue, test whether the problem occurs with a standard SDR resolution and with other capture applications closed. If the baseline works, include the exact feature that causes the failure, such as HDR10, P010, VRR, a high refresh rate, or a particular aspect-ratio mode.
Q: What is the fastest way to fix a NitLink resolution error?
Reconnect the HDMI and capture-card connections, close other capture applications, confirm Windows detects the device, and test a standard SDR resolution before enabling HDR or VRR.
Q: Why does NitLink show a black screen when the console works on a television?
The television may accept a signal that the capture card cannot capture. Test a supported SDR resolution and refresh rate, then verify the correct capture input is selected in NitLink.
Q: How do I fix a stretched NitLink image?
Check the source aspect ratio, NitLink scaling behavior, and the display's zoom or stretch mode. Preserve the source ratio and disable forced display stretching while testing.
Q: What information should I include in a support report?
Include the NitLink version, download source, Windows version, console, capture-card model, display, resolution, refresh rate, HDR or VRR state, reproduction steps, and Report ID when available.
Describe the last working configuration and the first setting that failed. That detail is more useful than reporting only that the screen is black.