Install tracy with Homebrew, Nix, scoop, winget

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• tracy
• tracy-capture
• tracy-csvexport
• tracy-import-chrome
• tracy-import-fuchsia
• tracy-profiler
• tracy-update

Project history

The public GitHub repository for Tracy was created in March 2020, and official release metadata includes v0.6.3 in April 2020. The repository has since grown into a large C++ codebase with profiler, capture, import, export, update, server, examples, documentation, and manual components.

The README describes Tracy as supporting CPU profiling with direct C, C++, Lua, Python, and Fortran integration, plus third-party language bindings, GPU profiling across major graphics and compute APIs, memory allocation tracking, locks, context switches, and frame-linked screenshots.

Release metadata shows sustained development through the 0.7, 0.8, 0.9, 0.10, 0.11, 0.12, and 0.13 lines, with v0.13.1 published in December 2025. The official releases include the PDF documentation and compiled Windows x64 binaries as assets, while package managers such as Homebrew, Nix, Scoop, and winget provide system-package routes.

Adoption history

Tracy's adoption is visible in both its official integration surface and its packaging footprint. The README calls out third-party bindings for languages such as Rust, Zig, C#, OCaml, and Odin, which indicates use beyond the directly supported C/C++-centered workflow.

The project page emphasizes games but explicitly includes other applications, and lists GPU APIs including OpenGL, Vulkan, Direct3D 11/12, Metal, OpenCL, CUDA, and WebGPU. That breadth made Tracy attractive to developers who want one profiler spanning CPU zones, GPU work, frame timing, memory, and synchronization behavior.

For package managers, Tracy is larger than a single executable: the Homebrew package exposes the GUI profiler plus capture, CSV export, import, and update tools. That makes the package useful both for interactive analysis and for scripted capture/export workflows.

How it is used

A typical Tracy workflow instruments an application with the client library, runs the profiler to connect to or open captures, and inspects frame timing, zones, samples, memory, locks, GPU events, and other telemetry in real time or from saved traces. Companion tools such as capture and csvexport support non-interactive and post-processing workflows.

The README directs users to the bundled documentation for usage and build instructions, to releases for the `tracy.pdf` manual and Windows binaries, and to an interactive demo. Video links on the README also show a release-by-release introduction path from older 0.x versions.

Why package nerds care

Tracy is a major package-nerd profiler because it packages a sophisticated native performance tool as reproducible command-line and desktop artifacts. It sits at the intersection of game-development tooling, systems performance analysis, and cross-platform package distribution.

Its Homebrew formula is notable for shipping multiple executables, while other package ecosystems expose it to Linux, Windows, and developer-shell workflows. For people who collect and compare developer tools, Tracy is the modern example of a high-end profiler that can still be installed with a package-manager command.

Timeline

• 2020-03: GitHub repository created.
• 2020-04: v0.6.3 release metadata published.
• 2020-06: v0.7 released.
• 2022-03: v0.8 released.
• 2023-10: v0.10 released.
• 2024-07: v0.11 released.
• 2025-05: v0.12 released.
• 2025-12: v0.13.1 released.

Related projects

• OpenGL, Vulkan, Direct3D, Metal, OpenCL, CUDA, WebGPU, Rust bindings, Zig bindings, C# bindings, OCaml bindings, Odin bindings, game-development profilers.

Sources

• https://api.github.com/repos/wolfpld/tracy
• https://github.com/wolfpld/tracy#readme
• https://github.com/wolfpld/tracy/releases
• https://github.com/wolfpld/tracy/releases/latest/download/tracy.pdf
• https://tracy.nereid.pl/
• source_facts.executables
• source_facts.package-manager