Framecap Studio starts from a deliberately small idea: the edit should be inspectable.
The recording stays as ordinary media. The cut, layout, zooms, cursor treatment, and output settings live in edit.json. Change that file and the preview follows. There is no hidden in-memory project state to reconcile and no second render path for export.
Why that matters
- Humans can read the decisions that shape a video.
- Agents can make precise changes without driving a visual editor.
- Git can show exactly what changed between two cuts.
- Preview and export consume the same source of truth.
That boundary is what lets Framecap feel like a local development server for video: edit the file, see the result, keep the artifact.
What comes next
The native app is the center of the workflow today. This site will document the product as it grows, host the practical details around releases, and eventually provide the small set of services needed for licensing and account operations.