How to translate a screenplay without losing formatting

To translate a screenplay while preserving its structure, work from the editable draft, keep screenplay elements identifiable during translation and inspect the final export. Review the language and the layout as separate tasks.

That distinction matters. A scene can be correctly formatted and mistranslated. It can also be accurately translated but difficult to read because character cues and dialogue have become ordinary paragraphs.

Start with the current editable screenplay

Keep an untouched copy of your source. Give it a draft date or version number and make sure it is the draft your collaborators expect.

Where available, use the screenplay's editable file, such as Final Draft FDX or Fountain. A PDF is useful as a visual reference, but converting it back into editable screenplay elements can introduce mistakes. Check a converted draft against the PDF before translating it.

Final Draft distinguishes formatted RTF export from plain-text TXT export; its export documentation notes that TXT contains text without formatting. Treat a plain-text export as something to inspect, rather than assuming it retains every screenplay distinction.

Keep each screenplay element attached to its purpose

Element	Check during translation
Action	The same visible action occurs in the same sequence
Character cue	The correct person speaks each line
Parenthetical	The direction stays attached to the intended dialogue
Dialogue	Meaning, relationship and register remain appropriate
Transition	Any retained transition remains distinguishable from action

Do not translate all capitalized text as if it were the same kind of element. A name in an action paragraph and a character cue may have different functions.

Check the dramatic distinction in a short exchange

This original Fountain example has two speakers and a parenthetical:

INT. KITCHEN - NIGHT

MAYA folds a letter into quarters.

MAYA
You said you wouldn't open it.

SAMIR
(without looking up)
I said I wouldn't read it.

An editorial Italian rendering illustrates the same structure:

INT. CUCINA - NOTTE

MAYA piega una lettera in quattro.

MAYA
Avevi detto che non l'avresti aperta.

SAMIR
(senza alzare gli occhi)
Ho detto che non l'avrei letta.

Illustrative source and editorial translation; not an INTERCUT output. These text blocks show screenplay elements, not final PDF pagination.

The scene depends on the distinction between opening and reading the letter. If both lines use the same verb, the exchange loses its point. If the parenthetical becomes action or moves to Maya's speech, the scene changes again.

This is a useful review habit: ask what must remain true for the exchange to work, then check whether the translated version preserves it.

Expect different line wrapping and pagination

Preserving screenplay structure does not mean preserving an identical page count. A translated sentence can take more space, words can wrap differently and the target language may require a different font.

Avoid squeezing text or margins to force the translated script onto the source's pages. Judge whether the result is readable and follows the format needed by the recipient. Use scene references or a bilingual comparison when collaborators need to compare versions.

Agree on recurring names and terms

Write a small glossary before reviewing the full script. Include character names, nicknames, place names, recurring objects and phrases whose repetition matters.

Record meaningful exceptions. A nickname used by one character may communicate intimacy or disrespect; replacing every instance with the formal name could erase that relationship. Decide where original spellings or transliterations help the intended reader.

For multilingual dialogue, identify lines that should remain in their original language. A blanket translation can remove a distinction the story needs.

Review dialogue as dialogue

Read key exchanges aloud. Check whether one character has become much more formal than another, whether a joke still has a setup and whether a threat has become an ordinary request.

An unfamiliar expression may need a choice between literal wording and its dramatic function. Make that choice consciously. An automated confidence score cannot decide every question of tone or intent for you.

Open the export in its destination

Inspect the editable file in a compatible screenwriting application and the reading file in a PDF reader. Do not rely solely on the web preview.

Check the beginning, middle and end, plus scenes containing long dialogue, parentheticals or multilingual text. If the script uses dual dialogue, revisions, scene numbering, notes or unusual elements, check those specifically and confirm what the tool supports.

For Arabic or mixed-direction text, inspect reading order, punctuation, names, numerals and font coverage. A visually plausible paragraph is not sufficient evidence that every exported format handles the script correctly.

A practical INTERCUT workflow

Start with an FDX or Fountain file and assess the free six-page preview. If you continue, use the available review tools to compare the translated draft with the source. Check the final files before sharing them.

Use the pricing page for current package scope and the privacy policy for processing information. Human review, where ordered separately, should specify the language, extent of review and deliverables.

Preview your screenplay translation · View pricing

Before you send the translated draft

Confirm the source version and target language.
Check that scene headings and speaker cues match the source's scene sequence.
Inspect the attachment of parentheticals and any special screenplay elements.
Check recurring terms and dialogue that carries a joke, threat or reversal.
Open the final export and inspect wrapping, page breaks and character coverage.
Confirm the recipient's format requirements and label the delivery clearly.