You cannot transfer input lag as an object. You can transfer a documented low-latency gaming setup: hardware connections, supported software, display state, game settings, accounts, save data, measurement method, and a known-good baseline. The receiving device or owner must reproduce and verify that state because different ports, panels, drivers, firmware, and background software can change the result.
Inventory the complete response path
Record input device model and firmware, wired or wireless mode, receiver and port, polling options, PC hardware, operating-system build, graphics driver, display model, cable, display port, resolution, refresh rate, variable refresh, frame cap, synchronization, window mode, overlays, capture tools, game build, and accessibility settings. Keep account names and secret values out of the handoff.
NVIDIA's system-latency guide separates latency into peripheral, PC, and display components. That model prevents a common mistake: blaming a network, controller, or graphics driver without measuring the end-to-end click-to-pixel path.
Create a baseline in a repeatable offline scene. Record the method, sample count, raw results, range, median, frame rate, and conditions. Network ping is useful for online responsiveness, but it is not a substitute for local end-to-end input-latency measurement.
Rebuild the display and device configuration
Connect the same device, receiver, cable type, and display port where practical. Use supported drivers and firmware from the manufacturer. Microsoft's refresh-rate guidance shows that Advanced display exposes resolution, refresh rate, and variable-refresh information; available rates depend on the display and some choices can change resolution.
Read back the active state rather than trusting a saved screenshot. Check the monitor's input, game mode, image processing, and on-screen refresh report if available. Reapply game settings one group at a time. Avoid importing unknown registry tweaks or disabling security, accessibility, anti-cheat, or device-management controls in pursuit of a lower number.
Move software and accounts without sharing credentials
The new owner should use their own permitted licenses and accounts. Transfer game saves only through supported platform methods, and verify whether progress is account-bound, device-bound, or portable. Remove personal tokens, browser sessions, cloud folders, and payment methods before handing over hardware. A configuration file may contain a username, server address, or path even when it appears harmless.
For drivers, Microsoft's Device Manager guidance documents update, reinstall, and rollback paths, notes that rollback requires administrator permission, and recommends Windows Update or the manufacturer's official source. Record the working version, but do not promise a rollback option until it is visible and authorized on the receiving system.
Make changes reversible
Before changing several layers, preserve personal files and save data through their own backup methods. Windows System Protection can create restore points for system files, applications, registry, and settings without changing personal files. Verify that it is enabled before relying on it; a restore point is not a complete file backup.
Change one layer at a time where possible. Define a rollback trigger, such as a repeatable regression beyond the baseline's measurement uncertainty. Keep an alternate cable, port, input device, or display available for isolation. Stop if the next step would breach warranty, tournament, anti-cheat, organizational, or security rules.
Run an acceptance matrix
Test at least the known offline scene, an ordinary game session, a restart, sleep and resume, input reconnection, and display reconnection. Confirm active resolution, refresh rate, variable refresh, frame cap, and driver after each relevant event. Compare results to the baseline using the same method and enough repetitions to distinguish noise from a real change.
Record every difference, accepted limitation, source, installer reference, owner, and recovery step. The transfer is complete only when the receiving owner can reproduce the documented state, recover from an approved change, protect their own accounts and saves, and independently verify that responsiveness meets the agreed threshold.
Sources
- System Latency Optimization Guide — NVIDIA
- Change the refresh rate on your monitor in Windows — Microsoft Support
- Update drivers through Device Manager in Windows — Microsoft Support
- System Protection — Microsoft Support