Windows gaming latency analyzer for input devices, CPU/GPU frames, scheduling, network, storage and audio.
Download for Windows x64 · Measurement guide · Report an issue
- Download Latency-Inspector-1.1.1-Windows-x64.zip from Releases and extract the whole folder.
- Run LatencyInspector.exe. Accept the administrator prompt for Windows kernel tracing.
- Open your game and select it in the process list. Game pipeline shows stages emitted by compatible instrumented applications, matched by PID, provider and frame ID. Missing stages remain unmeasured. Changing the selection starts a fresh measurement session.
- Play normally. Select a category or input device to inspect its graphs. Click a graph card for its exact definition.
- Use Export report to save measurements, percentiles, device identities and collector status as JSON.
Windows 10 version 2004 or later / Windows 11, x64. No runtime installation, account or subscription is required. Keep the bundled PresentMon.exe beside the application.
| Area | Available observations |
|---|---|
| Keyboard, mouse and HID controllers | Separate Windows Raw Input device views, message intervals and handler time; includes supported Windows HID views of gamepads. |
| Xbox / XInput / GIP | XInput state-query cost and packet-change intervals per slot; HID views when Windows exposes them; optional passive kernel transport observations. |
| Frames and GPU | Present intervals, CPU busy/wait, GPU busy/wait and queueing timelines, Present API time and software display estimates through Intel PresentMon. Availability depends on the game, graphics driver and presentation mode. |
| Game pipeline | Actual application marker pairs for simulation, render submission, Present and supported sleep/input-sample boundaries. PCL/Reflex and Intel application events are matched by PID, provider and full frame ID. No process injection is used. |
| CPU and system | ISR/DPC duration, including containing driver-image names where resolvable; observed thread ready-to-running waits, timer wake lateness, hard faults, CPU and memory usage. |
| Network | Synthetic IPv4 ICMP RTT, successive RTT variation, unanswered probes and TCP port 443 connection setup. Set the target in the top bar. These are separate from the game's network traffic. |
| Storage | Kernel disk read/write response times, plus selected-process I/O volume and attributed disk timings when issuing-thread ownership is available. |
| Audio | WASAPI default, minimum and current shared-engine periods, where exposed by the endpoint. |
Capture runs independently of graph updates. Graphs keep a bounded rolling window of 1,024 samples per metric, with p50, p95, p99 and session counts. Report & coverage explains unavailable sources and trace losses.
Measured means an elapsed interval between software timestamps. Reported means a value exposed by Windows. Estimated means a reconstructed timeline. A missing measurement stays unavailable; it is not displayed as zero latency.
Software alone cannot measure every physical delay. Input message cadence is not switch-to-game latency; an outstanding read includes waiting for input; PresentMon display estimates are not optical pixel measurements; audio periods are not physical sound latency. External hardware or application instrumentation is needed for those stages. See the measurement guide.
Attribution has explicit boundaries. The game-marker view measures elapsed time between markers for the same frame; this includes both work and waits. A driver DPC/ISR value is an inclusive routine interval, not proof that a mouse report spent that time in that driver. This version does not establish a USB-report-to-game-consumption link, isolate every third-party input filter's processing time, or join the new marker timeline to a particular GPU/display event. Those totals remain unmeasured rather than guessed. Fortnite-specific marker availability and accuracy have not been validated.
The passive KMDF filter records input request submission/completion timestamps, lengths and status codes. It never records report contents, changes inputs, blocks devices or creates virtual controllers. Association is per device; Windows class-wide filter lists are not modified.
The complete download includes the Microsoft-signed kernel probe in the Driver folder. No test certificate, test-signing mode or Windows security change is required. Windows/software collectors also work without installing the optional probe.
Open Kernel probe and use Install / associate probe, then restart Windows. New device associations also require a restart. Remove probe removes only this filter's associations and preserves other drivers. The console equivalent is LatencyProbeSetup.exe /install, /uninstall or /status; exit code 3010 means restart required. Setup retains the staged driver package during removal so active stacks remain safe until restart.
.\LatencyInspector.exe --capture 30 --output .\session.jsonThis runs a bounded capture without the dashboard. Reports contain device paths that can include serial numbers. Review them before posting publicly. No keyboard text, mouse positions or gamepad button/report contents are saved. Synthetic network probes go only to the IPv4 target configured for the session (default 1.1.1.1); measurements are not uploaded.
This repository contains downloads, documentation and issue tracking. Application, installer and driver source code remain private. There is no two-hour demo limit in Latency Inspector.
Frame analysis uses the bundled, unmodified Intel PresentMon 2.6.0, under its MIT license. PresentMon remains a separate process. See third-party notices and license.
This project, including its drivers, SDKs, libraries, applications, installers and examples, was created for lawful, constructive purposes such as accessibility, device customization, research, testing and software development. Illegal, malicious or unauthorized use is neither intended nor endorsed by TitanCSA or the contributors.
You are solely responsible for how you use, modify or distribute the software, for obtaining any necessary authorization, and for complying with applicable laws, third-party rights and service rules. TitanCSA and the contributors do not accept responsibility for users' actions, including illegal activity or misuse of the drivers or SDKs.
To the maximum extent permitted by applicable law, the software is provided "AS IS", without warranties of any kind, and TitanCSA and the contributors are not liable for claims, damages, data loss, system damage or other consequences arising from its use or misuse. Nothing in this notice excludes liability that cannot legally be excluded. Existing project and third-party license terms remain applicable.
Important
Full version and commercial licensing
Discord username: titancsa
Open Discord, choose Friends > Add Friend, enter titancsa, then send a direct message. Mention Latency Inspector and ask about the full / production version, commercial use or OEM redistribution.
Include your intended use and deployment size to discuss pricing, availability and the appropriate licensing / access instructions.
