150-Line Rust CLI Renders QR Codes in Your Terminal

The Simplest Fix for a Universal Developer Annoyance

Every developer knows the friction: a deploy preview URL is sitting in your terminal, your phone is on the desk, and bridging the gap between the two devices means fumbling with messaging apps, email drafts, or manual typing. A new open-source Rust CLI called ascii-qr eliminates that friction entirely — just run ascii-qr 'https://...' and scan the resulting QR code with your phone camera.

The tool clocks in at just 150 lines of Rust, compiles to a single static binary, and works everywhere — local terminals, SSH sessions, and even headless CI containers.

How Half-Block Characters Make It Scannable

Terminal-based QR renderers aren't new, but most produce codes that are too tall, too distorted, or simply unscannable. The key innovation in ascii-qr is its use of Unicode half-block characters to pack two QR modules into a single terminal cell.

Here's the concept: a standard terminal character cell is roughly twice as tall as it is wide. A naive approach — mapping one QR module to one character — produces a vertically stretched code that phone cameras struggle to decode. By using the Unicode upper-half block (▀), lower-half block (▄), full block (█), and space characters, ascii-qr encodes two vertical rows of QR data per line of terminal output.

This effectively halves the vertical height of the rendered code, producing a nearly square aspect ratio that matches what QR scanners expect. The result is a compact, reliably scannable code that fits comfortably in a standard 80-column terminal window.

Why 150 Lines Matters

In an era of bloated dependencies and complex toolchains, ascii-qr's minimalism is a statement. At 150 lines of Rust, the entire codebase is auditable in a single sitting. The compiled binary is statically linked, meaning there are zero runtime dependencies — no Python interpreter, no Node.js, no shared libraries to chase down.

This makes deployment trivial. Drop the binary into a Docker image, a remote server, or a CI pipeline, and it just works. For teams running automated deployments, the tool can generate QR codes for preview URLs as part of the build output, letting mobile QA testers scan and go without any copy-paste gymnastics.

Practical Use Cases Beyond Preview URLs

• SSH sessions: When you're logged into a remote server and need to transfer a URL to a local device, ascii-qr bridges the air gap instantly.
• CI/CD pipelines: Embed QR codes in build logs so team members can jump straight to staging environments from their phones.
• Conference demos: Presenters can flash a terminal QR code on a projector screen, letting audience members scan URLs without typing.
• IoT and embedded systems: Devices with terminal-only interfaces can surface configuration URLs or Wi-Fi credentials as scannable codes.

The Broader Trend: Unix Philosophy in Modern Tooling

ascii-qr is part of a growing movement of developers building hyper-focused CLI tools that do one thing well. Projects like ripgrep, fd, bat, and jq have demonstrated that small, fast, single-purpose binaries written in systems languages can replace or complement sprawling toolkits.

Rust, in particular, has become the language of choice for this class of tool. Its zero-cost abstractions, memory safety guarantees, and ability to produce fully static binaries make it ideal for utilities that need to run anywhere without ceremony.

Getting Started

The tool is available as an open-source project and can be installed via cargo install for anyone with the Rust toolchain set up. Pre-built binaries make it accessible even to those who don't write Rust.

For a 150-line investment, ascii-qr solves a genuinely annoying workflow gap — and it does so with an elegant technical trick that turns terminal limitations into a feature rather than a flaw.

Outlook

As remote development, containerized workflows, and mobile testing continue to grow, small bridging utilities like ascii-qr fill critical ergonomic gaps. Don't be surprised to see this pattern — tiny, dependency-free binaries that solve one specific cross-device problem — become even more common in 2025's developer tooling landscape.