The Editor

Write and edit your script in a split view, with a live preview on the same scroll sync as every viewer.

The editor window is the control surface: raw markdown on the left in a monospaced pane, the rendered script on the right. Both panes join the same scroll sync as the viewers, and every keystroke shows up in every viewer instantly.

Working with files

Action	How
New script	⌘N or File > New
Open a script	⌘O or File > Open
Reopen a recent script	File > Open Recent
Save	⌘S or File > Save
Save a copy elsewhere	⇧⌘S or File > Save As
Unsaved changes	Orange dot next to the file name

Your script stays a plain UTF-8 .md file on your disk. There is no library, no import step, and nothing leaves your Mac. Saving an untitled script prompts you for a location, and anything that would discard unsaved changes - New, Open, or quitting - asks first.

The editor window remembers its own size and position between launches.

Markdown reference

The viewers render a focused subset of markdown, tuned for reading at a distance:

Syntax	Renders as
# Heading	Largest heading, 1.9x the script font size
## Heading	Heading, 1.5x
### Heading	Small heading, 1.25x
- item or * item	Bullet line
**bold**	Bold
*italic*	Italic
`code`	Monospaced

Anything else renders as the text you typed. Links, images, tables, and fenced code blocks are deliberately not rendered; a teleprompter script is meant to be read out loud.

How lines map to the screen

Each line in your markdown is one paragraph on screen, so the rendered script keeps the exact line structure of the source. That is what lets every window agree on where “line 12” is, no matter the font size or window shape.

Practical implications:

• A blank line is spacing. Use blank lines freely to give your eyes anchor points.
• A long line wraps on screen but still counts as one line. Windows stay in sync through it by tracking how far into the paragraph you are.
• Headings are your section markers while recording. Reach a ##, glance, keep talking.