Where Does Tuba Store Accounts and Cache?
Tuba Mastodon client accounts and cache on Linux, covering Flatpak and native installs.
Last updated
Tuba is a GTK Mastodon client for Linux, shipped mostly as Flatpak. Sandboxed installs keep accounts, tokens and caches inside the app's .var tree. Native distro builds follow standard XDG roots instead.
Install method decides the path. Flatpak users back up one sandbox folder; native users chase .config and .local/share siblings. When the default looks empty, the other root usually holds the data.
Where Tuba stores this, by platform
~/.var/app/dev.geopjr.Tuba
Accounts, tokens and media cache for the Flatpak build, the most common install. Native packages split across ~/.config and ~/.local/share instead. Back up with Tuba closed; tokens sometimes demand fresh login on new hardware.
Frequently asked questions
Flatpak or native, where is my Tuba data?
It depends on the install. Flatpak keeps everything under the app sandbox path below; native packages follow XDG under .config and .local/share. Check both roots when migrating.
How do I move Tuba to a new computer?
Copy the Tuba data tree to the new machine and log back in. Tokens may need re authorizing as a security check, but timelines and drafts carry over.
Does Tuba only do Mastodon?
Yes, plus other Fediverse software speaking compatible APIs. Accounts are per instance either way, so each login stays separate inside the same data tree.
Notice an outdated path? Let us know.