Why it exists
Video research often happens inside the browser, while editing happens somewhere else. A useful moment appears, someone writes a rough timestamp, another source is opened, context gets split across notes, and the eventual handoff becomes a cleanup job of its own.
FootageMark narrows that problem. It keeps recorded-video ranges, source identity, clip type, optional editor context, and clip order together in a Chrome Side Panel workspace. The goal is not to replace an editor or a research system. It is to make the handoff between finding and editing less messy.
Why local-first
Research notes and source lists can be sensitive even when the source videos are public. FootageMark v1.0.0 does not require an account or a FootageMark backend. Projects are kept in Chrome local extension storage, and users can create their own JSON backup when they want a separate copy.
Why support is deliberately narrow
Web video players are not interchangeable. Some sites use nested frames, multiple media elements, autoplay advertising, or custom player behavior. Rather than marketing a generic “works on every video site” mode that can select the wrong media, FootageMark v1.0.0 limits advertised support to explicit integrations.
What FootageMark is not
It is not a downloader, an AI clip finder, a transcript extractor, a cloud collaboration service, or a frame-accurate NLE timecode system. Those are different products with different technical and legal expectations.
Part of RANURANU
FootageMark is one of the focused tools built under RANURANU. The shared idea is simple: solve one practical bit of friction clearly, keep the product lightweight, and let the collection grow one useful tool at a time.