- Home
- Game Profiling Software
- apitrace
apitrace
What it is
apitrace records OpenGL, Direct3D, and DirectDraw API calls in trace files for later replay and examination. Recorded calls can run on another machine, and OpenGL traces can be replayed across operating systems. Its tools expose call data, graphics state, framebuffers, and textures; they can edit traces and profile performance. Coverage spans OpenGL 1.0–4.5, OpenGL ES 1.0–3.0, Direct3D 7–11.x, and DirectDraw, with support varying by capture, replay, inspection, and profiling task. Command-line profiling can capture frame, GPU, CPU, and pixels-drawn data. Linux, OS X, and Windows support tracing, replay, command-line, and graphical use. Binaries are provided for Windows and Linux x86_64 and Arm64, plus Windows x86. The open-source MIT-licensed project is free, with a known limitation around programmatic Direct3D capture interfaces.
For and against
For
- Captures OpenGL, Direct3D, and DirectDraw calls
- Replays traces on other machines
- Includes CPU, GPU, and frame profiling
- Supports Linux, OS X, and Windows
- Open-source MIT license
Against
- Programmatic Direct3D capture interfaces are unsupported
- Feature support varies by API and operation
- Maintenance occurs as time permits
The verdict
apitrace combines graphics-call capture, replay, inspection, editing, and profiling in a free open-source package. Its API coverage varies, and programmatic Direct3D capture remains a stated gap.
Who it suits
apitrace suits developers analyzing graphics API behavior and performance on Linux, OS X, or Windows. It is useful when replay, trace inspection, framebuffer viewing, or profiling is needed.
Plans and prices
Open-source apitrace
source clone; binaries for Windows and Linux architectures
Read 1 Oct 2026 · apitrace.github.io
On the record
- Analysis
- The tools inspect state, view framebuffers and textures, view call data, edit trace files, and profile trace performance.apitrace.github.io · read 1 Oct 2026
- Annotations
- OpenGL traces can use several debug and marker extensions, including GL_KHR_debug and GL_EXT_debug_marker.github.com · read 1 Oct 2026
- API coverage
- The feature matrix covers OpenGL 1.0–4.5, OpenGL ES 1.0–3.0, Direct3D 7–11.x, and DirectDraw with varying trace, replay, inspection, and profiling support.apitrace.github.io · read 1 Oct 2026
- Backtrace capture
- Call-stack capture for OpenGL calls is available on Android and Linux.github.com · read 1 Oct 2026
- Downloads
- The project provides latest Windows and Linux binaries for x86_64 and Arm64, plus Windows x86 binaries.apitrace.github.io · read 1 Oct 2026
- Known limitation
- Programmatic Direct3D capture interfaces are currently unsupported.github.com · read 1 Oct 2026
- License
- The GitHub repository identifies the project license as MIT.github.com · read 1 Oct 2026
- Maintenance
- The project says it is maintained, but the maintainer has very little time and addresses patches, issues, and requests as time permits.apitrace.github.io · read 1 Oct 2026
- Operating systems
- The OS matrix lists Linux, OS X, and Windows for tracing, replay, CLI, and GUI use.apitrace.github.io · read 1 Oct 2026
- Profiling
- Command-line profiling can record frame, GPU, CPU, and pixels-drawn data, with shader-profile formatting available through a script.github.com · read 1 Oct 2026
- Purpose
- apitrace traces OpenGL, Direct3D, and DirectDraw API calls to files.apitrace.github.io · read 1 Oct 2026
- Remote replay
- qapitrace has rudimentary support for replaying traces on a remote target device.github.com · read 1 Oct 2026
- Replay
- Recorded calls can be replayed on any machine and, for OpenGL, on any operating system.apitrace.github.io · read 1 Oct 2026
- Source availability
- apitrace is open-source, hosted on GitHub, and can be cloned with its submodules.apitrace.github.io · read 1 Oct 2026
- Support
- The homepage links to a manual, bug-reporting guide, source-hacking guide, wiki, and mailing list.apitrace.github.io · read 1 Oct 2026
