Skip to content
EpicDraft Docs

Languages

EpicDraft has two independent language settings:

  • App language — the language of the interface (menus, settings, dialogs, toolbars). It applies to the whole app on this device.
  • Document language — set on a single script. It controls the script's text direction and the screenplay vocabulary used for that file, without changing the interface.

You can mix them: write an Arabic screenplay while keeping the interface in English, or vice versa.

App language

Open Settings → Language. Pick from:

  • Auto (System) — follow your device or browser language.
  • Any language in the list. Every language the interface ships in appears there — from Spanish, French, and German through Japanese, Korean, and Chinese to right-to-left Arabic, Hebrew, and Urdu.

The change applies immediately — no restart needed — and is remembered on this device. We aim to support as many languages as we can: more are on the way, and when a translation ships it simply appears in this list.

Two honest caveats. Translations are refined continuously, so if you spot awkward wording, we'd love to hear about it through the in-app feedback form. And the newest features can lag their translations slightly — an untranslated string shows in English until its translation catches up.

Document language

With a script open, go to Settings → File → Language and choose a Document Language. Leave it unset to inherit your app language (shown as Using default: …).

The document language list is much longer than the app language list. The app picker only offers languages whose interface translations actually ship; the document picker lists the whole language registry — every interface language and many more (Persian, for example) — because it only needs to know your script's writing conventions, not translate the whole app.

Setting a document language affects the script in two ways:

  • Text direction — right-to-left languages lay the page out right-to-left.
  • Screenplay vocabulary — scene-heading prefixes (INT. / EXT.), transitions (CUT TO:), times of day (DAY / NIGHT), and auto-inserted text like (CONT'D), (MORE), and the CONTINUED page marker are recognized and printed in that language. English keywords always keep working too, so pasting or importing an English script never breaks.

Screenplay fonts

Scripts that Courier can't render — Arabic, Hebrew, Japanese, Chinese, Korean, Devanagari (Hindi), Telugu, Tamil, Thai, and a few Latin, Cyrillic, and Greek edge cases — each have a dedicated screenplay font that both the editor and PDF export use, so what you see on screen is what prints.

To keep the app small these fonts aren't bundled; they arrive on demand:

  • On the web, the right font loads automatically the moment a document needs it — nothing to do.
  • In the desktop and mobile apps, the script's Language settings (Settings → File → Language) offer a one-tap download (the button shows the size), and a Downloaded fonts list where you can delete fonts you no longer need. Documents pick a newly downloaded font up automatically.

Every language in the picker has a font today. If you ever see a Limited support tag next to one, it means we've added that language before its screenplay font was ready: the editor falls back to one of your device's fonts and an exported PDF may show missing-glyph boxes for it. The document itself is fine, and it re-renders correctly as soon as the font ships.

Right-to-left scripts

For Arabic, Hebrew, and Persian:

  • The script area writes and lays out right-to-left when you set the document language.
  • The whole interface mirrors right-to-left when you set the app language to a right-to-left language.
  • PDF export embeds the right font and shapes and reorders the text correctly (including mixed right-to-left/Latin lines) on every platform — desktop, web, and mobile.

A few current limits worth knowing:

  • Bold or italic applied mid-word can interrupt Arabic letter joining in the exported PDF. Formatting whole words or lines is unaffected.
  • Persian doesn't have its own screenplay vocabulary pack yet, so scene-heading keywords stay in English (INT. / EXT.) until one ships. (Persian deliberately doesn't borrow the Arabic pack — the conventions differ.)

East Asian scripts (CJK)

Japanese, Chinese, and Korean work as both interface and document languages. The editor and PDF share a monospaced CJK screenplay font (downloaded on demand, per language), and line breaking and pagination follow the correct rules for full-width characters (including basic kinsoku line-break rules), so the on-screen layout and page counts are accurate.