Warp finally adds UI zoom, scaling more than terminal text

Warp has just rolled out UI zoom, bringing full-interface scaling to tabs, menus, and more—not just terminal fonts. The feature repurposes Warp’s DPI scale-factor system for smooth zoom via shortcuts or settings, while keeping font-only sizing intact.

Warp finally adds UI zoom, scaling more than terminal text

TL;DR

  • UI zoom: Scales the entire Warp interface, not just terminal text; addresses accessibility and high-DPI sizing mismatch
  • Scope: Applies to tabs, menus, icons, Warp Drive, and the command palette
  • Terminal font sizing retained: Separate key bindings still adjust terminal font size independently
  • Architecture constraint: Built in Rust with a custom UI framework; no Electron/webview zoom support
  • Implementation approach: Reused DPI scale factor by “faking” window size, then upscaling rendering
  • Controls: CMD +/- (Mac) or CTRL +/- (Windows/Linux); Settings → Appearance → Zoom for custom values

After years near the top of Warp’s request list, Warp’s UI zoom has finally landed—closing a long-running gap between terminal font sizing and scaling the rest of the app surface. Until now, the familiar CMD + on macOS (or CTRL + on Windows/Linux) only increased the terminal text, while tabs, menus, icons, and the rest of the interface stayed fixed in place. For accessibility needs or high-DPI setups, that mismatch made Warp’s otherwise crisp UI feel stubbornly small.

What “UI zoom” actually changes in Warp

Warp’s new zoom behavior scales the whole interface, not just terminal glyphs. The key difference is that UI zoom affects everything—including areas like Warp Drive, the command palette, and menus—rather than stopping at the terminal pane.

At the same time, Warp kept the prior option around: users who prefer the old behavior can still adjust terminal font size independently, using separate key bindings.

Why a seemingly simple feature took years

Warp isn’t built on Electron or a webview-based stack where zoom tends to come along for the ride. It’s written in Rust on a custom UI framework, which helps explain both the performance and the burden: features like full zoom require building the scaling behavior directly into the UI system.

A major blocker was early implementation debt. Many UI components were designed with hard-coded dimensions—fixed heights and widths that didn’t automatically scale with typography changes. Increasing font sizes without rethinking layout caused predictable breakage: tab titles getting clipped, icons drifting out of alignment, menus overflowing. Fixing it the “obvious” way meant touching a wide set of components, a chunk of work the team estimated at roughly three to four weeks—hard to prioritize amid ongoing features and bug work.

The mid-flight reframing: reuse DPI scaling

The eventual breakthrough came from treating zoom less like “make text bigger” and more like “scale the interface”—and noticing Warp already had a mechanism close to what it needed.

Warp already supports monitor DPI via a scale factor (for example, 2 on Retina displays). The solution was to reuse that same concept for zoom by “faking” the window size: if zoom is 2×, the UI framework is told the window is effectively half the size, then rendering is upscaled accordingly. The result is a UI that scales smoothly without manually reworking each component.

Once the idea clicked, the implementation work moved quickly. According to Warp’s Aloke Desai, the core change took about 20 minutes to code using Warp AI, followed by additional integration work for places like settings and the command palette.

How to use the new zoom controls

Warp now offers multiple paths to UI zoom:

  • Keyboard shortcuts: CMD + / CMD - on Mac, CTRL + / CTRL - on Windows to zoom in and out across the full interface
  • Settings: SettingsAppearanceZoom for a custom zoom value

Warp’s full Q&A, including the engineering trade-offs and the scale-factor approach, is available at the original post: https://www.warp.dev/blog/ui-zoom.

Continue the conversation on Slack

Did this article spark your interest? Join our community of experts and enthusiasts to dive deeper, ask questions, and share your ideas.

Join our community