A capture card viewer for Windows
Play your console in a Windows window. Keep Discord, your browser, and the rest of your desktop within reach, with HDR10 and variable refresh on supported setups.
Created and maintained by Klosed Lab. Official downloads and updates.
NitLink 1.2.5 is availableImproved source pacing, 4K X HDR detection updates, and Korean support.
Release notesComing soon on Steam
30 fps SDR console games at 60 fps.
Source frames
Displayed frames
A machine-learning model on your GPU adds a new frame between every two real ones. It runs inside NitLink, with no second program in the chain.
Experimental. Results depend on the game and your GPU. Frame generation adds delay; the game itself still runs at 30 fps.
See NitLink on Steam
Official NitLink channels
Download NitLink from the official GitHub releases. Follow NitLink on Steam for built-in frame generation.
Available now · MIT-licensed source
The capture viewer for playing your console on your Windows desktop.
Coming soon · Experimental frame generation
The capture viewer with experimental frame generation running on your PC GPU.
Both links are maintained by Klosed Lab. The source on GitHub is MIT-licensed. Community builds are maintained separately; use their maintainers’ release notes and support channels.
Inside NitLink
Press F1 to open the menu. Adjust your picture, sound, and window without leaving the viewer.
Choose your capture source, check the incoming signal, and control presentation from one menu. Switch capture cards and formats without restarting.
Low-Latency Mode, VSync, and display sleep controls are right beside your source details.
Control HDR10 output and aspect ratio, or enable NVIDIA Image Scaling for upscaling and sharpening.
HDR requires a compatible source, capture card, and display, with Windows HDR enabled.
See the HDR comparison
Adjust capture volume, mute the console, or tune the audio buffers from NitLink’s audio panel.
Adjustable audio buffering and device-clock drift correction help manage audio delivery. Buffer settings depend on what your card and driver can handle.
See current release notes
Go fullscreen, toggle picture-in-picture, or bring up the HUD from your keyboard. Resize, move, and fade the viewer to fit your desktop.
Alt + O toggles picture-in-picture. Ctrl + Arrows moves it around.
Check frame rate, app ingest time, GPU time, and pipeline status while you play. Press Ctrl + F3 to show or hide the overlay.
App ingest time is only part of the capture-to-display pipeline. It is not the total delay from your controller to the screen.
Play fullscreen, or pin your console in a corner. Share the NitLink window in Discord or capture it in OBS.
Source frame rate pacing compares captured pictures on the GPU to estimate unique-picture cadence. It can help compatible G-Sync or FreeSync displays follow the content; noise and subtle motion can affect the estimate.
Native HDR10
A native 10-bit capture path carries HDR10 from your console to your display. HDR detection and available capture formats depend on the card, signal and driver.
Requires an HDR display with Windows HDR enabled. The 4K S supports manual HDR at 1080p.
NitLink · Measured performance
NitLink presents captured frames as they arrive. In back-to-back tests against Elgato’s 4K Capture Utility, it was faster on the 4K Pro and 4K S, and statistically tied on the 4K X.
Historical baseline measured with NitLink 1.1 on the listed rig. These results do not measure the current release or frame generation and its added delay.
See how it was tested100 samples per app and card. Compare apps within each pair; different source modes do not rank the cards.
| Card / source | NitLink | Elgato | Difference |
|---|---|---|---|
| 4K Pro · 1080p144 | 38.4 ms | 44.2 ms | −5.9 ms |
| 4K X · 4K120 | 47.7 ms | 48.4 ms | Statistical tie |
| 4K S · 4K60 | 67.8 ms | 75.1 ms | −7.3 ms |
RTX 5080 · LG C3 OLED at 120 Hz · Windows 11 · NitLink 1.1 pre-release · June 5, 2026. Absolute results include the rig’s source and trigger path and are specific to this setup. Differences use unrounded medians.
NitLink walkthrough
An eight-minute walkthrough of NitLink, from setup to a PS5 Pro game. Recorded with NitLink 1.1; the interface has since been updated.
Watch on YouTube
YouTube loads only when you press play.
Cam Link 4K and Game Capture 4K60 Pro MK.2 are also supported. Other Media Foundation cards use the generic capture path.
4K Pro: PCIe, HDMI 2.1. Automatic HDR detection and live source details. VRR passthrough; 120 Hz capture uses a lower resolution.
4K X: USB, HDMI 2.1. Native controls expose source details. The 1440p60 HDR reconciliation correction is awaiting hardware validation; see issue #36. NitLink currently caps 4K P010 requests at 30 fps and uses SDR NV12 for 4K120. Negotiated modes depend on the source, USB connection and driver.
4K S: USB, HDMI 2.0. USB bandwidth limits HDR capture to 1080p. Use Alt + H to switch between 4K SDR and 1080p HDR.
Capture requirements: Windows 10 (1809+) or Windows 11, a DirectX 11-capable GPU, and Microsoft Edge WebView2. HDR and VRR require a compatible display and enabled Windows/display settings.
These are capture-viewer requirements. Check the Steam page for frame generation requirements. Other Media Foundation-compatible cards can use generic SDR capture, subject to their formats and drivers. Report your hardware results.
NitLink started with a PS5 and a 42-inch monitor that was already the main PC display. The goal was to play the console in a normal window, without switching inputs or adding another screen.
NitLink is created and maintained by Klosed Lab (nitlink-dev), with community contributions to code, translations and hardware testing. The source on GitHub is MIT-licensed. NitLink on Steam adds experimental frame generation.
Klosed Lab maintains the GitHub releases and NitLink Steam page linked here. Forks and community builds are maintained separately. For support, include the build name, version and download source.
NitLink on Steam will add experimental frame generation on your PC GPU. It targets 30 fps SDR games displayed at 60 fps. It adds delay and does not make the console render at 60 fps. The source distributed on GitHub remains MIT-licensed.
Yes. Connect your console to a compatible capture card attached to your PC. NitLink displays the card’s video and plays its audio on Windows. Frame generation also uses your PC GPU; see the Steam page for GPU requirements.
A capture card adds latency compared with a direct connection. NitLink minimizes the viewer’s part of that delay. For the least possible delay in competitive play, use a direct connection or HDMI passthrough. Low-latency presentation can tear on fixed-refresh displays.
Yes. Open the card in NitLink, then add NitLink as a Game Capture source in OBS. The same card can only be opened by one app at a time. Recording overhead depends on your hardware and OBS settings.
The supported Elgato cards deliver stereo PCM to NitLink. Set the console to Linear PCM, 2.0 channels, to avoid losing dialogue or other channels in the card’s downmix.
Pixel processing runs on the GPU. CPU work includes capture, frame handoff and audio. Usage varies with your card, resolution, GPU and processing options; one setup’s measurements are not a general hardware requirement.
The executable isn’t code-signed yet. Get it from the official GitHub releases. If you’ve verified the download and choose to run it, select “More info,” then “Run anyway.” The source is public.
Download the release ZIP, extract it, and run NitLink.exe. Keep the bundled files and folders together. Settings are stored in the working directory, normally beside the executable. You can support development through Ko-fi.
Get NitLink from the official GitHub releases. Follow NitLink on Steam for built-in frame generation.