Where Does Megalodon Store Accounts?
Megalodon for Android keeps sessions in private storage. Archived in 2025 with Moshidon as successor.
Last updated
Megalodon was an Android Mastodon fork whose ID extends the official client string with an sk suffix. Private storage holds sessions and cache. No iOS build exists. Drafts and prefs accumulate there. Instance data never needs file copies.
The project archived in May 2025 pointing users at Moshidon. Do not confuse it with the Megalodon JS library or a dinosaur game of similar name. Log into the same instances on the new client. Prefs exports move settings while sessions always re authenticate. Clearing the folder ends the session.
Where Megalodon stores this, by platform
/data/data/org.joinmastodon.android.sk
Private sessions and cache for the verified Megalodon package. Android only, archived 2025. Successor is Moshidon with separate storage.
Frequently asked questions
How do I move from Megalodon to Moshidon?
Install Moshidon and log into the same instances. Follows live server side. Megalodon exports cover prefs only; sessions re authenticate on the new client.
Is Megalodon still maintained?
Megalodon is org.joinmastodon.android.sk, forked from official org.joinmastodon.android. It has no iOS build and was archived in May 2025. Moshidon continues the line.
Notice an outdated path? Let us know.