a screenplay editor
uppercase is not a universal.
Screenplay software reads ALL-CAPS to tell a character cue from an action line. Most of the world's writing systems have no capitals at all. skript stores what each element is — so the format holds in Malayalam and Tamil exactly as it does in English.
one scene, three writing systems
the argument
case is a local peculiarity, not a property of writing.
Case exists in Latin, Greek and Cyrillic and essentially nowhere else. Arabic, Hebrew, Persian, Urdu, every Indic script, Chinese, Japanese, Korean and Thai are all uncased. An editor that recovers screenplay structure from capitals can only ever serve the minority of scripts that have them.
So skript never reads your text to decide what an element is. The type is state you set — with Tab, or a digit key — and it is saved in the document. Capitals on a scene heading are a display rule applied when you export, never a change to what you typed.
That one decision is why every element also carries its own language, so English scene headings and Malayalam dialogue live in one file — and why skript can tell you how your dialogue splits across languages, which an editor working on a text buffer cannot.
what works today
a drafting tool, finished enough to write a film in.
typed elements
Scene heading, action, character, parenthetical, dialogue, transition, lyric. Tab cycles the type without touching the text; a digit key jumps straight to one.
a language per element
Every element carries its own language and passes it to the next. One document, as many scripts as the film needs.
fountain in and out
Plain text on disk, with forced markers written every time so a Tamil line never parses as a character cue. Import what you wrote elsewhere.
nothing gets lost
Autosave, a version history that thins with age, and a copy mirrored to a file on your own disk every thirty seconds.
counted, not guessed
Speakers and their line counts, locations, dialogue against action, runtime per scene, and the split of dialogue by language. No model involved.
your outline, your notes
A scene navigator, tap-to-insert character cues, and a private pad per script that is never exported and never shared.
share one script, briefly
A read-only link that expires in seven days, made only when you ask. Your library never syncs. Nothing leaves the machine on its own.
on your desk, offline
Runs in a browser, installs as an app, works with no connection. Native builds for macOS, Windows and Linux from the same core.
what's coming
in the order it's being built.
No dates — the hard part is a layout engine and it isn't started. But the order is settled, and where something isn't here yet you should know what that costs you today.
pages and PDF
The layout engine: page breaks, page count, and a PDF written from the same glyph runs as the screen, so your count and the crew's count agree. Until it lands you will need another tool to produce a production PDF.
collaboration
A collaborator receives only the scenes they are working on, with their name on the copy. Today's share link is simpler than that and you should treat it as such — a readable copy, seven days, a link rather than a vault.
Final Draft files
Fountain round-trips today, so nothing you write is locked in. Reading and writing .fdx is queued — it is what collaborators will send you.
analysis that reads
The panel counts what is there and names its sources. Anything that interprets rather than counts comes later, opt-in, and your script is never sent anywhere to be read without you asking.
drafting on a phone
It installs and works offline on a phone now, which is enough to read and fix a line. Drafting wants a keyboard, and we would rather say so than pretend.
open it
start a script in your own language.
No account, no sign-up, nothing to install. Two bilingual samples are waiting inside — one Tamil, one Malayalam — so you can see the element typing and the script rendering work before you type a word.
browser · installs offline · macOS, Windows, Linux