.jmpr
One file for a whole production: screenplay, revisions, schedule, sides, signatures. Open spec under CC-BY. Free Rust reader. IANA media type and Apple UTI filed.
If Final Draft is .fdx, this is the version that opens in fifty years.
One container. One spec. Signed.
Filmmaking projects are dozens of files in incompatible formats. The script is .fdx. The schedule is a Movie Magic export. The sides are PDFs. The revisions are colored pages. The signatures are scanned. Nothing speaks to anything.
.jmpr is one container for all of it. Script, beats, shot list, schedule, sides, assets, manifests, signatures — one file, one spec, signed.
Open under CC-BY. Reader implementation in Rust, released under Apache-2.0. IANA media type filed. Apple UTI filed. Future-proof on purpose.
The container, by part.
- Manifest
- JSON-LD describing every asset, version, and signature in the container.
- Script
- The screenplay, in lossless internal format. Round-trips to FDX, PDF, Fountain, .jmpr.
- Revisions
- Page-locked, color-coded, hash-verified. Every revision is a signed event.
- Schedule
- Stripboard data. Constraints, cast holds, location days, union turnarounds.
- Sides
- Per-character, per-day, per-scene views. Generated from the script + schedule.
- Assets
- Mood boards, shot references, location photos, music cues — anything the project needs.
- Signatures
- Cryptographic signatures on every locked revision. Chain of custody from writer to set.
Where things stand.
- Spec
- drafted · v0.3 · public review
- Reader
- Rust crate, Apache-2.0, on crates.io
- IANA media type
- filed
- Apple UTI
- filed
- Inspector
- live · free forever
Next, in order.
- Conformance suite
Test fixtures + a CLI that grades any reader/writer against the spec.
on deck - Reference writer
Library to construct .jmpr from existing production files.
on deck - Browser viewer
Read-only .jmpr viewer in pure web tech.
on deck
Three doors in.
If you have a .jmpr file:
Drop it onto Inspector →If you want to write to it:
Reference writer is on deck. Email if you need it before it ships — /colophon.
Standards grow the category. The category grows the studio.
The .jmpr spec is open because a closed spec is a private file format with marketing. The format only matters if other tools adopt it — Final Draft, WriterDuet, Highland, Movie Magic, StudioBinder, every script-adjacent SaaS, every reader app. None of them adopt a format they can’t audit.
So the spec is CC-BY. The reader is Apache-2.0. The conformance suite will be open. The studio commits to backwards compatibility through v1.x. None of this is leverage. It’s infrastructure.