ScreenJSON (.screenjson) → Open Screenplay Format (.osf)
Pro Rescuing a script out of ScreenJSON (.screenjson) is the Pro part — from there it converts to Open Screenplay Format (.osf) and every other format on the site. The button below opens the converter with the output format already selected, and the server checks your plan when the file is dropped in.
Run this conversion
Convert ScreenJSON (.screenjson) → Open Screenplay Format (.osf)
Opens the homepage converter with Open Screenplay Format already selected as the output — drop your file, press Convert Script.
What survives this conversion
- typed screenplay elements in a strict JSON envelope
- page-chunked content that maps cleanly onto the canonical model
What can be lost
- adoption is small, so most OSF files are exports rather than originals
Every conversion includes an honest report listing anything that could not translate — you see it before downloading.
How this pair works
Your ScreenJSON file is parsed into a canonical screenplay model (by verified content, not just the file extension), then rendered as Open Screenplay Format. Open Screenplay Format background: The Open Screenplay Format was published in the early 2010s by Kent Tessman (Fade In’s author) as an open XML schema so tools could interoperate without licensing. Fade In saves it natively inside .fadein archives, and Scrite exports it.