Repository navigation
[FEATURE] Support multiple saved sessions, not just one auto-saved video #1787
Description
Activity
👋 Thanks for opening an issue, @magic-peach!
Our maintainers will review this shortly 🚀
Before you start working
- 📖 Read the CONTRIBUTING.md guide
- 💬 Wait for a maintainer to assign you the issue before starting work
- 🔍 Search for existing issues to avoid duplicates
For GSSoC'26 contributors
If you're contributing under GirlScript Summer of Code 2026, please mention it in your comment when requesting assignment:
"I'd like to work on this — contributing under GSSoC'26"
Architecture notes
Reframe is a static Next.js app with
output: "export". Key points:- All video processing uses FFmpeg.wasm (client-side, no server)
headers()innext.config.tswon't work — usevercel.jsoninsteadnot-found.tsxrequirespublic/404.html+vercel.jsonroutes config
Happy contributing! ⭐ Star the repo if you find it useful!
Feature description
src/lib/sessionDB.tsauto-saves the current video to IndexedDB under a single hardcoded key ("currentVideo", line 14) — only the most recent session ever persists; starting a new one silently overwrites the last.Problem this solves
A user working on multiple videos across sessions (e.g., resizing several clips for different platforms over a few days) currently loses access to anything but the last one they touched.
Proposed solution
Extend
sessionDB.tsto store multiple named/timestamped sessions instead of one fixed key, with a simple "Recent sessions" picker on load.Alternatives considered
None here is scoped narrowly to video file sessions — this is distinct from #1541 ("Custom Template Save Feature"), which is about saving reusable settings/recipe presets via localStorage, not saved video files with their edits.