- NitLink resolution not supported for resizing usually indicates a mismatch between the capture signal and requested window size.
- Start with the source signal by checking the console output, capture-card mode, and active Windows display settings.
- Test a standard resolution first before enabling HDR, VRR, high refresh rates, or unusual aspect ratios.
- Use native or proportional resizing when possible to reduce scaling conflicts and stretched output.
- Report persistent issues with the NitLink version, capture card, resolution, display mode, and diagnostic details.
What the NitLink Resizing Error Means
The message “NitLink resolution not supported for resizing” generally points to a display-scaling conflict. NitLink receives a video signal from a capture card, then presents that signal inside a resizable Windows window. If the requested size, source format, or output mode cannot be handled together, resizing may fail or the image may remain fixed.
This does not necessarily mean that the capture card is defective. The cause may be the console output, the capture device’s available modes, the Windows display pipeline, or an advanced feature such as HDR or VRR.
Video Highlights:
- NitLink displays a console signal through a Windows capture-card viewer.
- The setup depends on a working HDMI path and an available capture source.
- Window mode, full screen, and display configuration affect how the image is presented.
Use the following distinction when diagnosing the problem:
| Symptom | Likely area | First check |
|---|---|---|
| Error appears when dragging a window edge | Window scaling | Return to the original size and test a smaller resize |
| Image is visible but will not resize | Capture format or scaling mode | Check source resolution and aspect ratio |
| Black screen appears after changing size | Unsupported signal mode | Test SDR at a standard resolution |
| Image stretches horizontally or vertically | Aspect-ratio mismatch | Use proportional scaling or a matching window shape |
| Error begins after HDR or VRR is enabled | Advanced display mode | Disable one feature and test again |
NitLink supports features such as HDR10, VRR, low-latency presentation, picture-in-picture, screenshots, and recording. These features can create additional variables during troubleshooting. Isolate the basic video signal before testing advanced options.
Do not change several display settings at once. Confirm a stable SDR image in a normal window first, then re-enable HDR, VRR, or higher refresh modes individually.
Step-by-Step Resolution and Window Fix
Follow this sequence to identify whether the error comes from the source signal, capture device, Windows display mode, or NitLink’s presentation settings.
Confirm the HDMI Signal Path
Turn on the console or other source device before opening NitLink. Connect the source HDMI output to the capture card input, then connect the capture card to the Windows PC through its required USB or PCIe connection.
Check that the capture card is powered and visible to Windows. If the device is not recognized, resizing is not the first problem to solve. Close other applications that may be using the capture card, then restart NitLink after reconnecting the device.
Select the Correct Capture Source
Open NitLink and choose the available capture source that corresponds to the connected device. A wrong input, inactive source, or recently disconnected capture card can leave NitLink without a stable frame format.
If multiple video devices are listed, test them one at a time. Keep the setup simple until the image appears consistently.
Test a Standard SDR Mode
Temporarily disable HDR on the console and in Windows. Use a conventional SDR output mode supported by the console, capture card, and display. Avoid combining HDR, VRR, high refresh rates, and resizing during the first test.
A stable SDR image provides a baseline. Once resizing works in that mode, restore advanced features one by one.
Resize Proportionally
Resize the NitLink window by dragging a corner rather than forcing an extreme width or height. Keep the window’s shape close to the source aspect ratio. If the image becomes stretched, return to a proportional shape and check the aspect-ratio setting.
Test both a smaller window and a larger window. If only one direction fails, the limitation may be tied to the requested presentation size rather than the source connection.
Re-enable Display Features Separately
After the basic window works, enable HDR or VRR separately. Confirm the display supports the selected feature and that Windows is configured for the same mode. If the resizing error returns, disable the most recently enabled feature and compare the result.
Record which setting changes the behavior. This makes a future support report more useful and avoids repeating the full setup process.
| Test order | Configuration | Purpose |
|---|---|---|
| 1 | SDR, standard resolution, normal window | Establish a basic working signal |
| 2 | SDR, resized window | Test NitLink window scaling |
| 3 | HDR enabled | Check high-dynamic-range presentation |
| 4 | VRR enabled | Check variable-refresh behavior |
| 5 | HDR and VRR together | Test the combined advanced setup |
If HDR, VRR, refresh rate, aspect ratio, and window size change together, it becomes difficult to identify the setting that triggered the error.
Capture Card and Display Compatibility Checks
Resolution resizing depends on more than the monitor’s maximum specification. The source console, HDMI path, capture card, Windows capture device, NitLink, graphics output, and display must all handle the selected mode consistently.
NitLink’s official compatibility guidance focuses on capture devices such as Elgato 4K Pro, Elgato 4K X, and Elgato 4K S, while other devices may require individual testing. Compatibility can vary by input format, HDR state, refresh rate, and whether the device is connected through USB or PCIe.
Source Device
- Confirm the console is outputting an active signal
- Test a standard SDR mode first
- Avoid unsupported refresh-rate combinations
Capture Card
- Check Windows device detection
- Confirm the selected input
- Close software competing for the device
Windows Display
- Match the active display mode
- Check HDR and VRR state
- Keep scaling behavior consistent
| Hardware area | What to verify | Why it matters |
|---|---|---|
| Console output | Resolution, refresh rate, HDR state | Determines the incoming signal format |
| Capture card | Input mode and Windows detection | Determines whether NitLink receives usable frames |
| USB connection | Direct connection and stable power | Reduces device initialization problems |
| PCIe connection | Device installation and driver visibility | Ensures the internal card is available to Windows |
| Monitor or TV | Resolution, HDR, and VRR capability | Controls the final presentation environment |
| HDMI path | Correct input, output, and cable routing | Prevents unstable or missing signals |
When using HDMI pass-through, confirm that the capture card can capture the same mode it passes to the separate display. A television may accept a signal that the capture path cannot expose to Windows in the same way.
For HDR workflows, verify the complete chain:
- The source is actually outputting HDR10 content.
- Windows HDR is enabled when required by the presentation path.
- The display is in an HDR-capable mode.
- The selected pixel format is supported across the capture and graphics path.
- The color range is interpreted consistently.
For VRR workflows, confirm that the display and graphics hardware support variable refresh. Keep the presented frame rate within the display’s supported VRR range, and use a Present Cap when necessary to leave headroom below the maximum refresh rate.
A capture card may work in one resolution or color mode but fail in another. Treat compatibility as a combination of device, resolution, refresh rate, HDR state, and connection path.
Advanced Fixes for Scaling, HDR, and VRR
If basic SDR resizing works but the error returns after enabling advanced features, use a controlled comparison rather than reinstalling immediately.
Check the aspect ratio
A console signal may use a fixed aspect ratio while the NitLink window is being resized to an unrelated shape. Use a proportional window shape and avoid forcing the image to fill every available pixel. If the picture looks stretched, compare the source resolution with the NitLink aspect-ratio setting and the display’s own scaling mode.
Compare low-latency and synchronized presentation
NitLink includes low-latency and synchronization-related controls such as VSync and Present Cap. These settings affect how frames are presented, but they do not replace a compatible source format. Test low-latency mode with a stable source first, then compare VSync and frame-pacing behavior if tearing or uneven motion appears.
| Scenario | Suggested first configuration | Main goal |
|---|---|---|
| Competitive console title | Low Latency enabled, stable refresh rate | Reduce presentation delay |
| 30 FPS source | Matched Present Cap, even frame pacing | Avoid uneven frame delivery |
| VRR display | VRR enabled, cap below display maximum if needed | Maintain a stable variable-refresh range |
| HDR troubleshooting | HDR only, with other advanced options unchanged | Isolate color and format behavior |
| Resizing troubleshooting | SDR, normal window, proportional shape | Verify basic scaling support |
Test HDR and P010 carefully
HDR problems can appear as gray blacks, washed-out highlights, or incorrect brightness. If the selected workflow uses a 10-bit format such as P010, confirm that the capture path, graphics driver, and display all support it. Disable HDR temporarily if you need to determine whether the resizing message is tied to the high-dynamic-range path.
Reinitialize after hardware changes
Restart NitLink after reconnecting a capture card, changing the active Windows display, switching audio or video devices, or changing the source output mode. Reinitialization can help the application detect the current device state rather than relying on an earlier signal configuration.
Resolution Error Checklist:
- Confirm the console HDMI output is active
- Verify that Windows recognizes the capture card
- Select the correct NitLink capture source
- Test SDR at a standard resolution
- Resize the window proportionally
- Re-enable HDR or VRR one feature at a time
The most dependable troubleshooting pattern is baseline first, advanced features second: stabilize SDR resizing, then test HDR, VRR, frame pacing, and alternate display modes individually.
When to Report the Issue
If the message remains after the basic signal and display checks, prepare a concise diagnostic report. The official support workflow recommends including the NitLink version, download source, capture card, source device, resolution, and diagnostic Report ID when available.
Use the official NitLink FAQ for general support guidance and the NitLink GitHub Issues page for reproducible technical problems. The official GitHub project also provides the project context and release information.
| Report detail | Example format |
|---|---|
| NitLink version | Exact version shown by the application |
| Download source | Official GitHub release or Steam version |
| Source device | Console model and output mode |
| Capture card | Brand, model, USB or PCIe connection |
| Display | Monitor or television, HDR and VRR capability |
| Resolution state | Source resolution, refresh rate, SDR or HDR |
| Trigger | Resizing, full screen, HDR, VRR, or another change |
| Result | Error text, black screen, stretch, crash, or fixed size |
| Report ID | Include the diagnostic ID when NitLink provides one |
Before submitting, reproduce the issue with the smallest useful setup:
- Close other capture and recording applications.
- Restart the source device, capture card, and NitLink.
- Test a standard SDR signal.
- Confirm whether normal window mode works.
- Repeat the resize action and note the exact point of failure.
- Restore advanced features one at a time.
Do not describe the issue only as “resizing does not work.” Explain whether the error appears during window dragging, full-screen switching, HDR activation, source changes, or display changes. That distinction helps separate scaling behavior from signal compatibility.
Include the exact error text, the last setting changed, the working baseline mode, and the first mode that fails. This creates a clear comparison instead of a general compatibility request.
NitLink Resolution FAQ
Q: What does “NitLink resolution not supported for resizing” mean?
It usually indicates that the requested NitLink window size or scaling behavior is incompatible with the current capture signal, aspect ratio, or display mode. Start with a stable SDR signal and resize proportionally.
Q: Should I disable HDR and VRR when troubleshooting resizing?
Temporarily disabling HDR and VRR is a useful isolation step. Once normal SDR resizing works, re-enable HDR or VRR separately to identify whether an advanced mode changes the result.
Q: Can a capture card work at one resolution but fail at another?
Yes. Capture behavior can vary by resolution, refresh rate, color format, HDR state, and connection path. A device may work in a standard SDR mode while requiring additional checks for HDR, VRR, or high-refresh input.
Q: What information should I include in a support report?
Include the NitLink version, official download source, source device, capture-card model, connection type, display, resolution, refresh rate, HDR or VRR state, exact trigger, observed result, and diagnostic Report ID when available.