Where Does PixelDroid Store Accounts and Data?
PixelDroid keeps accounts and cache in private storage under its F-Droid package, with photos on the Pixelfed instance. Filenames stay unpublished.
Last updated
PixelDroid is free-software Pixelfed photos with unpublished internals. Accounts and media live on instances while tokens and cache sit in private storage. Build files confirm Room plus preferences without filenames.
Loops covers official short video under its own package while PixelDroid handles third-party photos. Multi-account spans servers with drafts undocumented. Quote package plus tech stack, never file names.
Where PixelDroid stores this, by platform
/data/data/org.pixeldroid.app
Private storage for the verified F-Droid package with Room plus prefs tech and unpublished names. Photos live on instances with tokens local. Root needed for direct reads.
Frequently asked questions
Where are PixelDroid photos stored?
They live on the Pixelfed instance with client tokens and cache local. Multi-account support spans servers while drafts stay undocumented. Quote the package with Room-plus-prefs tech, never filenames.
PixelDroid or Loops package?
It is the third-party F-Droid photo client while Loops is the official short-video app with its own package. Purposes differ across photo and video with separate IDs. Quote each package for its own app.
Where is the PixelDroid database?
Through SQLite Room plus SharedPreferences per build files without published names. Generic private trees need root with adb-only access. Server content refetches while tokens persist locally.
Notice an outdated path? Let us know.