How to clear Overture's local cache safely
A safe step-by-step for clearing only Overture's browser-side data — keeps your events untouched and skips the nuclear "clear everything" option.
When to clear the cache
Overture stores a small amount of data in your browser to keep the app fast and to remember your preferences across sessions — things like which theme you picked, which org you were last viewing, and a handful of UI hints. This local data is almost never the problem, but very rarely a stale entry can make the app act strangely (icons missing, a logo not refreshing after upload, a weird ghost session in a tab that shouldn't be there).
If the system status check looks green and a refresh hasn't fixed it, clearing the Overture cache is a safe next step. Nothing on your event server is affected — events, rows, follow-ups, and members all live on the server, not in your browser. Clearing the cache only removes preferences.
The 60-second fix — hard reload first
Try this before anything more aggressive. A hard reload bypasses the browser's file cache without touching local data:
- Windows / Linux —
Ctrl+Shift+R(orCtrl+F5) - macOS —
Cmd+Shift+R
If a hard reload solved it, you're done. If not, move on to the cache clear.
Clearing local storage for app.overture.show only
This is the safest option — it only clears data for the Overture app, leaving every other site alone (your Gmail tabs stay signed in, your Notion stays signed in, etc.). The exact path depends on your browser:
Chrome, Edge, Brave, or Arc
- Go to app.overture.show.
- Open Developer Tools —
F12on Windows, orCmd+Option+Ion macOS. - Click the Application tab at the top of the DevTools panel.
- In the left sidebar, expand Storage and then Local Storage.
- Right-click
https://app.overture.showand choose Clear. - Close DevTools and refresh the page. Overture will sign you out — sign in again, you're done.
Safari
- Open Safari → Settings → Privacy.
- Click Manage Website Data.
- Search for
overture.show, select the row, and click Remove. - Close the settings window and reload the Overture tab. Sign in again.
Firefox
- Open Settings → Privacy & Security.
- Scroll to Cookies and Site Data and click Manage Data.
- Search for
overture.show, select it, and click Remove Selected. - Save and reload Overture. Sign in again.
What this clears — and what it doesn't
- Clears: your saved theme choice, last-viewed org, in-app dismissed hints, your sign-in session cookie. Result: a fresh signed-out app.
- Does not touch: your events, sessions, rows, follow-ups, members, venues, photos, or anything on the Overture server. All of that lives in the cloud and reloads when you sign back in.
- Does not touch: your saved passwords — your browser's password manager is separate from site storage.
Don't use "Clear all browsing data"
Browser-wide "Clear browsing data" controls clear everything for every site — you'll be signed out of every web app on your computer. Use the Overture-only steps above unless a support agent specifically asks you to clear everything.
Still seeing the problem
If clearing the cache didn't fix it, send a quick report:
- The browser and OS you're on (e.g. "Chrome 138 on Windows 11").
- What you were doing when the problem started.
- The current Overture version — see How to check Overture's version.
Email it to [email protected] or use the in-app Support button (the life-ring icon in the top toolbar). See How to report a bug to support for what we'd like to see in the message.