A Rust-built vision overlay engineered for clarity, restraint, and quiet reliability.
rust-vision-overlay is a lightweight rendering layer written entirely in Rust, designed to draw contextual information on top of a game window without disturbing the underlying process. It exists because most overlay tooling in this space is bloated, fragile, or built on stacks that age poorly — this project takes the opposite approach: small binary, minimal footprint, predictable behavior.
The domain of Rust ESP Undetected tooling has historically been synonymous with sketchy binaries and opaque behavior. We think that's backwards. A well-built overlay should behave like any other piece of serious software: versioned, documented, inspectable in its architecture, and honest about what it does and doesn't guarantee. This README treats it that way.
This project is for people who want to understand how an overlay is built — the rendering pipeline, the memory-safe design choices Rust affords, and the tradeoffs between detection surface and feature richness — rather than just grabbing a black-box executable. If you're evaluating tools in this space and care about maintainability, this is written for you.
-
Overlay compositing — renders directly on a transparent layer above the game window; no pixel-level screen scraping required.
-
Low-latency draw loop — the render thread targets sub-frame update intervals so on-screen markers track their targets without visible lag.
-
Configurable visual layers — toggle boxes, distance labels, or skeletal markers independently; each layer is its own module.
-
Memory-safe core — written in Rust with
unsafeblocks isolated and audited, reducing the class of bugs that plague C++-based overlay tools. -
Undetected-by-design philosophy — minimizes footprint through careful process interaction rather than aggressive hooking, keeping the tool's signature small and predictable.
-
Hot-reloadable config — settings apply live; no restart cycle required when tuning colors, opacity, or thresholds.
-
Built-in performance HUD — optional frame-time and draw-call counter for users who want to self-diagnose stutter.
-
Portable single binary — one
.exe, no scattered DLLs, no background installer service.
Tip
Start with default settings before customizing anything. The defaults are tuned for the widest range of displays and refresh rates — most tuning issues disappear once you understand the baseline.
-
Visit the landing page using the download button above.
-
Download the current build — always grab the latest tagged release from the page, not an older mirror.
-
Run the executable directly. There's no installer wizard and no background service left behind.
-
Launch your game first, then start the overlay — this ordering matters for clean window attachment.
Note
No package managers, no dependency installers, no scripts to run beforehand. The binary is self-contained by design.
| Component | Requirement |
|---|---|
| OS | Windows 10 (64-bit) or Windows 11 |
| Architecture | x86_64 |
| Dependencies | None — statically linked |
| Disk space | Under 50 MB |
| GPU | Any DirectX 11+ capable GPU |
Important
This tool is Windows-only. There is no macOS or Linux build, and none is planned — the overlay technique relies on Windows-specific compositing APIs.
The tool follows a deliberately short pipeline — fewer moving parts means fewer failure points and a smaller behavioral footprint.
- Attach — the process identifies the target window handle without altering its memory space aggressively.
- Read — a minimal set of read-only queries pulls the coordinates needed for rendering.
- Transform — screen-space projection converts world data into 2D draw coordinates.
- Render — the overlay layer draws boxes, labels, or lines on a transparent surface.
- Loop — the cycle repeats at a tuned interval, balancing responsiveness against resource use.
flowchart LR
Attach --> Read --> Transform --> Render --> Loop
Why this design minimizes detection surface
By avoiding deep code injection and favoring read-only queries plus an independent render surface, the tool keeps its interaction with the target process shallow. Shallow interaction generally means a smaller, less distinctive footprint — though no overlay tool can promise permanence against evolving anti-cheat heuristics.
Q: The overlay window is transparent but nothing draws. A: Confirm the game is running in windowed or borderless mode — exclusive fullscreen can block overlay compositing entirely.
Q: Frame rate drops when the overlay is active. A: Disable the performance HUD and reduce active visual layers; each layer adds a small render cost.
Q: The tool doesn't attach to the game window. A: Launch the game first, wait for the main menu to load, then start the overlay — attaching too early can fail silently.
Q: Colors look washed out on my monitor. A: Check your Windows HDR settings; overlay transparency renders differently on HDR-enabled displays.
Q: Antivirus flags the executable. A: This is common for unsigned overlay binaries. Review the source and build it yourself if you need full assurance.
Warning
No overlay tool can guarantee permanent undetectability. Anti-cheat systems update continuously — treat "undetected" as a current state, not a promise.
-
Default theme — dark, low-opacity panels designed to stay unobtrusive at a glance.
-
Alternate themes — high-contrast and minimalist variants selectable from the settings panel.
-
Keyboard shortcuts:
Key Action InsertToggle overlay visibility F1Open settings panel F2Toggle performance HUD Ctrl+EndSafely close the application -
Settings persistence — all preferences save automatically to a local config file, no cloud account required.
Contributions are welcome — whether that's a bug report, a documentation fix, or a pull request improving the render pipeline.
- Open an issue with a clear reproduction case before submitting large changes.
- Keep pull requests scoped — small, reviewable diffs merge faster.
- Discussions and feature proposals belong in the Discussions tab, not in issues.
We maintain a friendly, low-drama community. Be specific, be patient, and be kind to first-time contributors.
Released under the MIT License, 2026.
This project is provided for educational and research purposes related to graphics programming, overlay rendering, and Rust systems development. Usage of this tool may violate the terms of service of certain games or platforms — that risk and responsibility rests entirely with the user. The maintainers do not endorse, encourage, or take responsibility for any consequences arising from its use.