Where Does Loops by Pixelfed Store Videos and Drafts?
Loops videos live on your home instance server in the fediverse. Drafts and cache sit in private app storage and the camera roll.
Last updated
Loops has no central video folder because there is no center. Your account belongs to a home instance, and that server stores your profile, follows, and published loops. Federation then spreads them to compatible apps across the fediverse, which is why the same clip can surface on Mastodon.
The phone holds the working copies: camera takes, drafts, sounds, and cache. Publish moves the durable copy to your instance. That split decides backups. Export from the server or your account settings for the real archive, and treat the app reinstall as the moment local drafts die.
Where Loops by Pixelfed stores this, by platform
/storage/emulated/0/Android/data/com.pixelfed.loops/files
Drafts and cache in private storage; published videos on your instance server. Exact folder names may vary by version. Save takes to the gallery before reinstalling.
Loops app storage (Settings > iPhone Storage)
Same server-side model as Android. Drafts live in the app sandbox and camera roll. Export account data from the instance for a durable copy.
Frequently asked questions
Who actually hosts my Loops videos?
Your home instance holds the account and the videos, and ActivityPub carries them to Mastodon and Pixelfed feeds. You can migrate instances later or export data. During the beta, keep your own copies of anything important since backups are best effort.
How do I save a draft before posting?
Record in the app camera and post straight away. Unposted takes stay as drafts in the app or save to the camera roll first. The app needs Android 8 or iOS 16.4 at minimum, and posting requires a login on some instance.
Notice an outdated path? Let us know.