Where Does Loops Store Drafts and Data?
Loops keeps accounts and videos server-side on the fediverse with photo-library exports. No local drafts file is verified.
Last updated
Loops is server-side video with a photo-library exit. Accounts and clips live on fediverse servers behind content delivery, with gallery saves as the only local artifacts that matter. Draft persistence rides the same server model.
Package and bundle IDs verify cleanly across stores with Expo internals underneath. Generic sandbox paths describe OS convention rather than Loops files, so this post quotes IDs plus behaviors. No local drafts file survives verification.
Where Loops stores this, by platform
/data/data/com.pixelfed.loops
Private sandbox for the verified Loops package with Expo storage internals unpublished. Drafts persist server-side with gallery export as the local artifact. Quote the package, not inner files.
Frequently asked questions
How do I keep a Loops draft?
Save a copy to the photo library from the app where offered. Drafts persist server-side with local caches in Expo storage that stay undocumented. Generic sandbox paths name OS convention, not Loops files.
How do Loops videos reach my gallery?
Through camera, microphone and photo permissions that prove the media flow. Saves land in the library only when downloading or keeping copies. Server plus CDN hold the canonical videos.
What is the Loops app identifier?
It identifies the verified Android package and iOS bundle with store IDs on both. Expo storage details stay internal with secure store for secrets. Quote IDs confidently and file paths carefully.
Notice an outdated path? Let us know.