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

margin reads stored type

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

enough to write a film in, and hand it to a crew.

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. Two people talking at once sit side by side. Paste a scene from anywhere and it arrives typed; copy one inside skript and every line stays what it was.

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. Type Manglish or Tanglish in Latin letters and it arrives as Malayalam or Tamil, word by word.

it learns your script

Characters, locations and times of day are suggested from what you have already written, the ones you use most and most recently first. Enter takes one. Rename a character everywhere in a single undo; find and replace anything else, lit on the page as you type.

fountain and final draft, in and out

Plain text on disk, with forced markers written every time so a Tamil line never parses as a character cue. Open a collaborator's .fdx and send one back. Keep the whole project — languages, pad, version history — in one .skript file of your own, or lay it out as plain text for an email. The title page is a page you edit, and it travels in the file; scene numbers can too.

your old script, back

A script typed years ago in ML-TT Karthika, Bamini or TSCII looks like Malayalam or Tamil and is not — the PDF cannot be searched or edited. Drop it here and get real text back, scenes and speeches sorted, ready to open. It is read in your browser; the page is not able to send it anywhere.

nothing gets lost

Autosave, a version history that thins with age, and the apps keep a copy of every script as you write. In a browser and on a computer, a copy can also go to a file on your own disk every thirty seconds.

pages, and a PDF

The page count you see while writing is the one on paper: both come from the same layout. Export writes the PDF — US Letter, (MORE) and (CONT'D) where a speech crosses a page, a title page. Malayalam and Tamil are set properly and stay searchable. The same file gives the same pages on a Mac, on Windows and in a browser, to the byte.

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, and a private pad per script written in the same screenplay elements, pulled over the page when you want it. It leaves only in your own project file, never in an export you send. Typewriter scrolling, if you like the line you are on to stay put.

what leaves the machine

Nothing you write. Your library never syncs, and the seven-day share link was switched off in September 2026 because it kept a readable copy on a server — it comes back encrypted or not at all. The one thing sent automatically is a daily count of which theme and layout you opened, carrying nothing that identifies you, and you can switch that off.

on an iPhone and iPad

The Apple apps wear Apple's own controls: your scripts in a list you swipe, a toolbar for scenes, find, the pad, analysis and history, and a bar above the keyboard with every element type one tap away. Open a .fountain or .fdx from Files; export a PDF straight back to it. In beta on TestFlight.

on your desk, offline

Runs in a browser, installs as an app, works with no connection. There is a Windows app to download, and a Mac, iPad and iPhone beta on TestFlight; the Linux build exists and is not out yet. A menu bar — File, Edit, Format, View — for anyone who looks for one.

what's coming

in the order it's being built.

No dates. But the order is settled, and where something isn't here yet you should know what that costs you today.

next

a page view

The page count and the PDF now come from a layout engine of our own, so your count and the crew's count agree. The screen itself still wraps the way a browser does; drawing it sheet by sheet from the same engine is next. So is A4, and fonts for scripts beyond Malayalam and Tamil — until then Hindi, Telugu or Kannada text will not print in the PDF.

then

collaboration

A collaborator receives only the scenes they are working on, with their name on the copy. The seven-day share link that came before it is switched off: it kept a readable copy on a server, which is the thing collaboration has to get right rather than repeat.

later

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.

later

drafting on a phone

The iPhone app has the element bar above the keyboard now, and typing Manglish turns autocorrect off so it cannot rewrite a word first. Whether a whole film can be drafted on a phone is what the beta is for — it has not yet been tried on one, 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 · Windows app · Mac, iPad & iPhone beta · PDF out