Where Does Granola Store Notes and Cache?
Granola keeps its local cache in Application Support on Mac and Roaming Granola on Windows, with notes in a versioned cache JSON file.
Last updated
Granola's local folder is small and practical. On Mac it is ~/Library/Application Support/Granola and on Windows it is the Roaming Granola folder. Two files do almost all the work: supabase.json for auth and a versioned cache file for notes with raw transcript segments.
There is no Linux desktop build, so no Linux path belongs here. Treat the cache file as transient. Granola's changelog lists local cache encryption as underway, which means today's readable JSON could turn opaque after an update. Export anything load-bearing while it still reads as text.
Where Granola stores this, by platform
~/Library/Application Support/Granola
Holds supabase.json with API credentials and cache-v3.json (later versions use higher numbers) with notes plus transcript segments. Quit Granola before copying since the cache rewrites while running. Reach it via Finder Go to Folder because Library is hidden.
%APPDATA%\Granola
Same layout as Mac: supabase.json for auth and a versioned cache JSON for notes. Paste the path into Explorer. No Linux desktop app exists, so this folder plus the Mac one are the only desktop locations.
Frequently asked questions
Which Granola files do I back up before reinstalling?
Copy cache-v3.json (the number rises with updates, so look for cache-v*.json) plus supabase.json while Granola is quit. That pair carries notes with transcript segments plus login. The vendor flags local cache encryption as in progress, so exports may stop working in future builds.
Where is my Granola login token stored?
Check the same folder for an access token entry tied to WorkOS. Deleting the Granola folder signs you out on that machine only. Your cloud meetings stay in your account and return on next login.
Where is the Granola folder on Linux?
There is none. Granola ships Mac, Windows, iOS and Android builds with no Linux desktop app. Third-party CLI docs mention a hypothetical Linux path, but no vendor build writes it, so it is omitted here.
Notice an outdated path? Let us know.