Fix ExoPanda UI Broken — Zoomed Or Cropped

What You'll See

The ExoPanda UI loads, but the contents look wrong. The most common variants:

• The whole layout is zoomed in, like the page magnified itself by 20–40%.
• The corners are pinched or warped — rounded edges look pulled.
• The right side or bottom is cropped off, so buttons sit half outside the window and you can't click them.
• Sometimes only one panel is affected; sometimes the whole window is.

The app's logic isn't broken when this happens — macros that were already running keep running. What's broken is the picture you're looking at.

Why It Happens — Tauri + WebView2

ExoPanda is built on Tauri 2, a desktop framework that puts a native window around a small embedded browser. The browser engine it uses on Windows is WebView2 — the same engine that powers Microsoft Edge. Tauri handles the window itself; WebView2 paints everything inside it.

That means “the ExoPanda UI” is, technically, a tiny web page being drawn by WebView2 inside a Tauri-managed window. When you see the UI render zoomed, pinched, or cropped, what's happened is WebView2 fell into a rare rendering edge case — usually a DPI handoff or a viewport-size mismatch — and the browser engine is drawing the page at the wrong size relative to the window Tauri gave it.

The frustrating part: it's a quirk of the framework, not a bug in our code. WebView2 and Tauri's interaction with high-DPI displays, multi-monitor setups, and the occasional graphics driver update isn't always clean, and there's only so much an app on top can do about it.

What It Isn't

Two things this is not, before you go chasing them:

• Not Windows display scaling. Scaling causes a different problem entirely — the macro refuses to start at all. If that's your symptom, see Fix ExoPanda Macro Not Starting instead.
• Not a Roblox problem. The Roblox client doesn't know about the ExoPanda window. This is purely how WebView2 is drawing our app on your machine.

What You Can Try

Be straight with you: there's no one-click fix because it isn't really fixable on our side. That said, things that have helped people:

1. Fully quit and reopen ExoPanda. Right-click the tray icon → Quit. Reopen the app. A fresh launch often hands WebView2 a cleaner DPI value.
2. Update the WebView2 runtime. Open Microsoft Edge once and let it update, or grab the latest WebView2 runtime from Microsoft directly. WebView2 ships independently of Windows updates, and an older runtime catches this bug more often.
3. Restart Windows. Especially relevant if you just plugged in or unplugged a second monitor, or just woke the machine from sleep — both can leave DPI state stale.
4. Move the window to your other monitor and back, if you have one. Sometimes that triggers WebView2 to recalculate sizing and the UI snaps back to normal.
5. Resize the window. Drag the corner to a different size, then back. Same idea — forces a re-layout.

What We're Doing About It

We're tracking the cases that come in to see if there's a pattern (specific GPU drivers, mixed-DPI setups, recent Windows builds, etc.). Long term, if the WebView2 edge case turns out to be unfixable from our side, swapping the UI framework is on the table — it's a heavy change, so we're not rushing it, but it's an option if the bug keeps biting people.

Related Guides