Capture card input lag is the delay between your controller input, what your gaming PC renders, and what you actually see and interact with through the capture pipeline. You cannot eliminate it entirely, but you can shrink it enough that gameplay feels immediate. With the right settings, most setups can move from a noticeably sluggish preview to a responsive pass-through that is hard to distinguish from a direct monitor connection. Realistic gains come from fixing the biggest bottlenecks first: how the signal is routed, how the preview is rendered, and how your system encodes video. Expect the largest qualitative improvement from switching to hardware pass-through, with smaller but cumulative gains from encoder, resolution, and sync tweaks as of early 2026.
Quick Wins
Use this table to prioritize. Start at the top and test after each change with the same game scene and controller.
| Change | Effort | Expected gain |
|---|---|---|
| Use HDMI pass-through to gaming monitor, play from pass-through not preview | Low | Large to very large |
| Set capture software preview to low-latency mode and disable buffering | Low | Moderate to large |
| Match capture card EDID / input resolution and refresh to source | Low | Moderate |
| Switch encoder to hardware (NVENC / AMF / Quick Sync) and lower canvas to 1080p60 | Low | Moderate |
| Set USB capture card to USB 3.0+ port with dedicated controller, disable USB selective suspend | Low to moderate | Small to moderate |
| Disable V-Sync in game and in capture preview, cap FPS slightly below refresh | Low | Small to moderate |
| Update GPU driver and capture card firmware, set Windows GPU preference to High Performance | Moderate | Small to moderate |
Step-by-Step Tuning
Work in order. Each method includes what causes lag, how to check it, what to do, and how to undo it. Test one change at a time.
1. Play From HDMI Pass-Through, Not the Preview Window
What causes it: Software preview must go through the capture card, USB or PCIe bus, system memory, and your streaming app before it reaches your eyes. That chain adds buffering by design. The card’s HDMI Out / Pass-Through port bypasses the PC entirely.
How to check: Route Console HDMI Out > Capture Card HDMI In, then Capture Card HDMI Out > Gaming Monitor HDMI In. Open your capture app. If you are moving your character while looking at the app’s preview, you are adding the full pipeline delay.
What to do: Connect pass-through as above with an Ultra High Speed HDMI cable. Set your monitor input to the pass-through HDMI port. In OBS Studio go to Settings > Video and keep canvas at 1920×1080. Keep the OBS preview open only for monitoring stream health, not for playing. For dual-PC setups, keep your gaming PC’s monitor on DisplayPort or HDMI directly from the GPU, and send a cloned HDMI output to the capture card on the streaming PC.
Trade-off: You lose the convenience of playing windowed on the streaming PC. You will need to glance at the preview for stream alerts.
How to undo: Disconnect pass-through and return to HDMI Out directly from console or GPU to monitor.
2. Enable Low-Latency Mode and Disable Buffered Preview
What causes it: Capture apps buffer a few frames to smooth playback and avoid tearing. That buffer equals added latency.
How to check: In OBS Studio, right-click the Video Capture Device source > Properties. Look for Buffering. In Elgato 4K Capture Utility go to Settings > Device. In AVerMedia RECentral go to Settings > Capture Device > Advanced.
What to do: In OBS Studio Properties for Video Capture Device, set Buffering to Disable, set Video Format to MJPEG or NV12 if available for your card, and set Color Range to Partial. Click Deactivate then Activate to reload. Then go to Settings > Advanced > Video and set Renderer to Direct3D 11 and Color Format to NV12. In Elgato software, set Input EDID Mode to Display and toggle Low Latency Mode to On. Restart the app after changing.
Trade-off: Disabling buffering can introduce occasional preview stutter if your system is under load, but pass-through play remains unaffected.
How to undo: In OBS Properties set Buffering back to Enable or Auto, and in vendor utility set Low Latency Mode to Off.
3. Match Resolution, Refresh Rate, and EDID Exactly
What causes it: When the source, card, and monitor disagree on resolution or refresh, the card or GPU rescales and frame-converts, which requires a frame buffer.
How to check: On Windows press Win + I > System > Display > Advanced display. Note the refresh shown for your gaming display. On console go to Settings > Screen and Video > Video Output on PS5 or Settings > General > TV & display options on Xbox. Compare to OBS Settings > Video > FPS and the capture card’s reported input in its properties.
What to do: Set the console or gaming PC to 1920×1080 at 60Hz or 2560×1440 at 120Hz only if your card explicitly supports that mode on the box. In Elgato 4K Capture Utility go to Settings > Device > EDID and select Display Passthrough or Internal, then choose 1080p60 from the dropdown. In AVerMedia Gaming Utility go to EDID Settings > Default EDID > 1080p60. In OBS set Settings > Video > Common FPS Values to 60 and set Output > Scaled Resolution to match source with Rescale Output unchecked for the recording path you are testing. Set the card’s Video Input to Auto or the exact mode, not Custom scaling.
Trade-off: You may need to give up 4K120 capture if your card tops out at 1080p60 or 1440p60 pass-through, but latency drops and compatibility improves.
How to undo: Return EDID to Default and restore source to its previous resolution and refresh.
4. Use Hardware Encoding and Reduce Canvas Load
What causes it: Software x264 encoding on the CPU competes with the game and capture pipeline, increasing render and encoding queue depth. High canvas resolutions increase GPU load before the frame is even sent to the encoder.
How to check: In OBS go to View > Stats. Watch Rendering Lag and Encoding Lag while capturing. Press Ctrl + Shift + Esc to open Task Manager > Performance and see CPU and GPU utilization. If Rendering Lag rises above zero, the GPU is bottlenecked.
What to do: In OBS go to Settings > Output > Output Mode > Advanced. Set Encoder to NVIDIA NVENC H.264 if you have an NVIDIA GPU, or AMF H.264 for AMD, or QuickSync H.264 for Intel. Set Rate Control to CQP with CQ Level 18 to 23 or CBR 6000 to 8000 Kbps for testing, Preset to P5 Quality or Quality, and Keyframe Interval to 2. Go to Settings > Video and set Base Canvas to 1920×1080 and Output Scaled to 1920×1080, Downscale Filter to Bicubic. Close other GPU-heavy sources or browser docks while testing.
Trade-off: Hardware encoders use slightly more GPU budget and may produce marginally softer text at low bitrates compared to slow x264 presets, but input responsiveness improves.
How to undo: In Output settings switch Encoder back to x264 and restore previous canvas resolution.
5. Fix USB and PCIe Bandwidth and Power Settings
What causes it: USB 2.0 ports, hubs, and power saving cause polling delays and bandwidth throttling. Internal PCIe cards can be starved if placed in a low-bandwidth slot or sharing lanes.
How to check: In Windows go to Device Manager > Universal Serial Bus controllers. Right-click USB Root Hub > Properties > Power Management and see if Allow the computer to turn off this device is checked. Check Device Manager > Sound, video and game controllers for your capture card name and whether it reports as USB 3.0. For internal cards, check motherboard manual for which PCIe x1 or x4 slot is directly connected to CPU vs chipset.
What to do: Plug USB cards directly into a USB 3.2 Gen 1 or Gen 2 port on the rear I/O, not a front-panel hub. Avoid USB hubs. In Windows go to Control Panel > Hardware and Sound > Power Options > Edit Plan Settings > Change advanced power settings > USB settings > USB selective suspend setting and set to Disabled. In Device Manager, uncheck Allow the computer to turn off this device for each USB Hub. For PCIe cards like Elgato HD60 Pro or AVerMedia Live Gamer 4K, seat in a PCIe 3.0 x4 or x1 slot that does not share bandwidth with the GPU, and in BIOS set PCIe Link State Power Management to Off under Power Management.
Trade-off: Disabling power saving slightly increases idle power draw and may keep fans active longer.
How to undo: Re-enable USB selective suspend and Power Management checkboxes, or move the card back to the previous port.
6. Control Sync: Disable Extra V-Sync and Cap Frame Rate
What causes it: Double V-Sync, where both the game and the capture preview sync to refresh, queues frames. Unlimited frame rates create a render queue that also adds delay.
How to check: Look for V-Sync On in game graphics settings and in NVIDIA Control Panel > Manage 3D Settings > Vertical sync or AMD Software > Graphics > Wait for Vertical Refresh. Check if monitor reports G-Sync or FreeSync active in its on-screen display.
What to do: In game set V-Sync to Off. In NVIDIA Control Panel go to Manage 3D Settings > Global Settings, set Vertical sync to Off, Low Latency Mode to On, and Max Frame Rate to 3 frames below your monitor refresh, for example 57 for 60Hz or 117 for 120Hz. In AMD Software go to Gaming > Graphics > Radeon Anti-Lag to Enabled and Frame Rate Target Control to 57 or 117. If you use G-Sync or FreeSync, enable it on the monitor but keep capture preview V-Sync off. In Windows go to Settings > System > Display > Graphics > Change default graphics settings and set Hardware-accelerated GPU scheduling to On, then reboot.
Trade-off: Without V-Sync you may see occasional tearing in the preview window, though pass-through on a VRR monitor stays smooth.
How to undo: Set Vertical sync back to Use the 3D application setting and set Max Frame Rate to Off.
7. Update Drivers, Firmware, and OS Scheduling
What causes it: Old GPU drivers, capture firmware, and default Windows scheduling add overhead and compatibility fallbacks that increase pipeline latency.
How to check: In Device Manager > Display adapters note driver date. In capture utility check Settings > Device > Firmware Version against the vendor readme. In Windows go to Settings > System > Display > Graphics and check the GPU preference for OBS Studio or your capture app.
What to do: Install the latest NVIDIA GeForce Game Ready Driver or AMD Adrenalin driver with Perform a clean installation checked. Update card firmware via Elgato Game Capture 4K Capture Utility > Settings > Device > Firmware Update or AVerMedia Assist Central > Update. In Windows Settings > System > Display > Graphics, add OBS Studio executable at C:\Program Files\obs-studio\bin\64bit\obs64.exe and set to High performance. In Settings > Gaming > Game Mode set Game Mode to Off when using a dedicated streaming PC, or On when single-PC gaming and capturing, then test both. Restart after updates.
Trade-off: New drivers can occasionally introduce other issues, so keep the previous installer handy.
How to undo: In Device Manager > Display adapters > Properties > Driver > Roll Back Driver, and reinstall previous firmware from vendor support archive if needed.
Measure Before and After
You need a repeatable test that does not rely on feel alone. Do this without invented numbers by comparing visual timing.
Phone slow-motion method: Set your phone to slow-motion video at 120 or 240 fps. On your gaming monitor enable a visible reaction cue, such as firing a weapon or opening a menu. Record a clip that shows both your controller thumb pressing a button and the screen in the same frame. Count frames between press and on-screen action using your phone’s frame-by-frame playback or free tools like VLC with the E key to advance frame by frame. Run the same test looking at pass-through versus looking at the capture preview. You should see fewer frames of delay on pass-through. Save two clips labeled before and after.
OSD timer method: In OBS add a Text source with a millisecond timer via OBS Tools > Scripts or a clock overlay on the gaming PC, display it on the gaming monitor, and capture it. Compare the timer value seen on the gaming monitor directly versus the timer value visible in the OBS preview screenshot taken at the same instant with Win + Shift + S. A smaller difference means lower pipeline delay.
Log check: In OBS go to Help > Log Files > View Current Log. Search for rendering lag, encoding lag, and dropped frames. Also open %appdata%\obs-studio\logs and review the latest log for warnings about buffering or device timestamp issues. Repeat measurements after each change and keep notes in a text file at Documents\capture-lag-notes.txt so you can revert what did not help.
What Not to Do
Do not play from the software preview if a pass-through port exists. Preview is for the audience, not for you. Even with low-latency modes, it will always trail pass-through.
Do not use a USB hub or USB 2.0 port for a USB 3.0 card. Hubs split bandwidth and introduce polling variance. Use a rear motherboard port.
Do not upscale or frame-rate convert in the capture card. Leave scaling to the GPU or avoid it entirely by matching source and canvas. Extra scaling stages queue frames.
Do not stack display sync and capture sync. Do not enable V-Sync in game, in the GPU control panel, and in the capture renderer at the same time.
Do not run network-heavy preview features while testing. Disable OBS browser sources, chat docks, and NDI preview during latency tests to isolate capture delay from network or browser load.
Do not install two capture utilities fighting for the same device. Close RECentral, 4K Capture Utility, or other vendor apps when using OBS to avoid exclusive-mode conflicts.
FAQ
Do I need a PCIe card to get low lag?
Not necessarily. A PCIe card like the AVerMedia Live Gamer 4K or Elgato HD60 Pro has an advantage because PCIe bandwidth is higher and more consistent than USB, which helps maintain low-latency modes. However, a modern USB 3.0 card on a dedicated USB 3.2 Gen 1 port with buffering disabled and pass-through play can feel equally responsive for 1080p60. Choose PCIe if you have a free slot and want the most stable 1440p or high-refresh capture.
Why is there lag only in OBS but not on my TV?
Your TV is showing the HDMI pass-through signal directly, while OBS shows the capture pipeline. To confirm, mute OBS preview audio and compare. Fix it by playing from the pass-through monitor, disabling buffering in Video Capture Device properties, setting Output color to NV12, and matching FPS between source and OBS Settings > Video. Also check that View > Stats shows zero rendering lag.
Does 4K60 capture add more lag than 1080p60?
Yes, in practice it increases load on the capture chip, encoder, and GPU, which can increase buffering to keep up. If you need 4K for recording but want low lag while playing, set the console to output 1080p60 for competitive sessions and keep 4K60 only for single-player capture, or use a card that supports 4K60 pass-through while capturing at 1080p60 via downscale in Settings > Video.
Can a splitter reduce lag instead of pass-through?
A powered HDMI 2.0 or 2.1 splitter can be equivalent to pass-through if it is a true 1-in 2-out splitter with one output to monitor and one to capture card, with no scaler. Avoid splitters that advertise built-in downscaling or EDID mixing, as they buffer. When testing a splitter, verify in Windows Advanced display settings that the gaming monitor still reports the correct refresh, and in OBS that the card reports the same resolution without rescaling.
