UGC workflows move fast, but client contracts and platform policies move carefully. Raw footage often cannot sit on a third-party server by default. Local-first editing keeps clips on your device until you explicitly choose cloud backup or upload.
repli.ac follows that model. The hook editor stores templates, word lists, and export batches in your browser. Rendering happens client-side. Optional Premium cloud backup is opt-in, not the default path.
What stays on your machine
When you work without cloud features, these items remain in IndexedDB and local storage on your browser:
- Uploaded video clips and thumbnails.
- Caption templates, word-slot lists, and layout preferences.
- Finished export batches and stitch settings.
- Onboarding and editor walkthrough state.
Clearing site data or switching browsers without backup means that local library is gone. Export finished batches to disk when a test wraps so you keep deliverables even if browser storage is cleared.
When cloud backup helps
Premium cloud backup suits creators who switch devices or want a safety net for recordings from the browser studio. Clips upload via Cloudinary and associate with your account in Supabase. You control when uploads happen; the editor does not silently sync every file.
Agency teams can still run entirely local for sensitive client work and enable cloud only for internal test assets. The two modes coexist in one account based on how you use each feature.
Speed without a render farm
Local rendering avoids queue time on shared infrastructure. Your machine does the work while you preview the next batch. For typical hook lengths and batch sizes, that tradeoff favors iteration speed over offloading to a remote encoder.
Very large batches or long clips will still take time. Plan exports when you can leave a tab open, and use cancel controls if you need to stop a run mid-batch.
Privacy and client trust
Explaining where footage lives is part of client onboarding. Local-first means you can truthfully say raw clips never left the editor machine unless you turned on cloud backup or used sign-in features that upload media. Read the privacy policy for full detail on account and optional cloud data.
Practical habits
- Download export ZIPs before clearing browser data.
- Use descriptive batch names tied to client or campaign codes.
- Enable cloud backup only for clips you are comfortable storing remotely.
- Keep a local copy of winning hooks even when cloud sync is on.
Edit hooks locally on your next project.