Create, organize, import, and export teleprompter scripts
Create rich-text teleprompter scripts, organize personal and team work, add markers and pauses, and import or export supported formats.
Finish the Getting Started Checklist
The sidebar checklist follows the core EasyPrompter workflow: open or create a script, run the teleprompter, add a marker, and customize the reading setup. Select an incomplete item to open the first available script in the appropriate editor or teleprompter view. If you do not have a script yet and your role allows creation, EasyPrompter opens the new-script editor. Talent users return to the scripts list until a shared script is available.
The reading-setup item opens the teleprompter with Prompter Settings visible. Checklist steps complete automatically when you perform the corresponding action.
Organize Your Teleprompter Script Library
The Scripts dashboard keeps personal and team content in separate sidebar sections. Use the Recent Scripts and Starred Scripts views for quick access, or open a collection to narrow the list.
Sort and Change Views
Use the toolbar to enter selection mode, change the sort order, show starred scripts first, or switch between grid and list layouts.
Find Scripts Quickly
Click Search in the sidebar or press Cmd+K on macOS or Ctrl+K on Windows. Search includes scripts and collections, and it also provides a shortcut for creating a script.
Create a Script in Context
The New Script split button adapts to where you are:
- In a Collection → creates the script inside that collection
- In Team Scripts → creates a Team (shared) script
- Anywhere else → creates a Personal (private) script
Use the import action beside New Script to choose a .txt, .ezp, or .docx file instead.
Import Word and Text Scripts
Drag .txt, .ezp, or .docx files onto the scripts list or a collection page to import. Multiple files can be dropped at once. Dropping onto a collection automatically adds the script and inherits its privacy level.
| Format | Import | Export | Notes |
|---|---|---|---|
Plain Text (.txt) | ✅ Free | ✅ Free | |
EasyPrompter (.ezp) | ✅ Free | ✅ Free | Native format with full formatting |
PDF (.pdf) | ❌ | Premium | Requires internet |
Word (.docx) | ✅ Premium | ✅ Premium | Requires internet for export; import works offline |
Importing files in the editor
Two entry points:
- Sidebar New Script import action → "Import File (.txt, .ezp, .docx)"
- Script editor ⋮ menu → "Import / Export" submenu → "Import (.ezp, .docx, .txt)", then choose:
- "Replace Current Content": overwrites the current script
- "Import as New Script": creates a new script via API immediately (no draft state) and navigates to it
- "Cancel"
What a Word import keeps and drops
The import produces only what you could rebuild with the editor toolbar, and it never invents anything.
Kept: bold, italic, underline; text colors and highlights (matched to the closest EasyPrompter color family, so they stay readable in dark and light themes); center and right alignment; left indentation (each half inch is one indent level); bullet and numbered lists as real lists, with each Word level as its own indented list and numbering continuing where Word continued it; headings and Title as bold, Subtitle as italic; tabs; All Caps text (imported in uppercase).
Dropped: images, shapes, and text boxes (including any text inside a text box); footnotes, endnotes, and comments (including their reference marks); hyperlink URLs (the link text stays); strikethrough, subscript, superscript, fonts, and font sizes.
Things that surprise people:
- Paragraph spacing is not imported. Space before or after a paragraph in Word never becomes a blank line. Only blank paragraphs that exist in the document come through. If your script relies on spacing for pauses, add blank lines or Pause markers in the editor.
- Page breaks and soft returns each start a new paragraph, with no blank line added.
- Tables are flattened to one paragraph per cell, in row order. A two-column video/audio script interleaves the columns.
- Scripts built entirely in text boxes import as empty, because text-box content is removed. Convert the boxes to normal paragraphs in Word first.
- Files with no text (for example, only images) are refused with a "no text to import" message rather than creating an empty script.
Whenever a table, image, text box, note, comment, heading, or color was simplified, the import shows a short summary of what changed, either in the Replace / Import as New dialog or as a notice after the import.
If your imported file has a title that matches an existing script, a "Script Already Exists" dialog appears. Choose "Keep Both" to import as a new script with a sequential suffix (e.g., " (2)"), or "Overwrite" to replace the existing one. Cancelling aborts the import with no changes.
Import from Legacy EasyPrompter
Signing up from a legacy EasyPrompter link takes you straight into the migration wizard. You can also open Settings, then Migration, at any time to import scripts from your legacy EasyPrompter account. If you can import into more than one workspace, choose the destination. When that destination supports Studio sharing, you can also choose whether the imported scripts are private or shared with the workspace. Personal and non-Studio destinations stay private automatically, so they do not show a visibility choice. EasyPrompter places the scripts in a collection named Imported from EasyPrompter 3.
Scripts with an Imported badge already have an active imported copy, but you can select them again. Use Select un-imported when you want only scripts that have not been copied yet. If your selection includes previous imports, EasyPrompter asks you to confirm the single script by name or the number of affected scripts. A confirmed re-import creates another independent copy using the next available sequential title. It does not overwrite the existing copy or change the legacy original.
The imported scripts and collection appear in the library immediately. If the destination differs from your current workspace, Open collection switches to the correct workspace before opening it. Large imports show batch progress. A partially completed import keeps unfinished scripts selected so you can retry them safely. After the subscription transfer is complete, its finished controls stay hidden while script import and optional re-import remain available through the migration window.
Edit a Script
The editor combines the script title, visibility, sharing, formatting tools, script content, save state, metadata, and the Start Prompter action on one screen.
Use Markers and Pauses
- In the editor toolbar, click Marker to insert a bookmark at your cursor position
- In the teleprompter, press ] and [ to jump between markers
- Click Pause to insert a timed break (default 1 second; click the pause to adjust duration)
Move Scripts Between Workspaces
Drag a script card from the content area onto My Scripts or Team Scripts in the sidebar (the target highlights with a blue ring). You can also use the script's ⋮ menu → Move to Team / Move to Personal.
When moving team → personal, explicit shares and collection memberships survive. Only org-wide implicit access is removed.
Select Multiple Scripts
- Click Select in the toolbar to enter selection mode
- Click and drag on empty space to draw a marquee rectangle (auto-enters selection mode)
- Shift+Click to select a range between the last-clicked and target script
- Cmd+A / Ctrl+A to select every script in the current filtered view, including cards that have not finished loading their details
Drag any selected card to move the full selected set to a sidebar collection, workspace, or Trash target. The same rules apply as for a single script: items already in the destination are skipped, permission-changing moves are confirmed once for the affected set, and workspace-specific Trash targets accept only matching scripts. Moving multiple scripts to Trash also requires confirmation. Each script's privacy and collection changes complete together or not at all.
While offline, every selected script must already be available offline. If any selected script is unavailable, EasyPrompter blocks the whole drag and explains that you need to reconnect or cache the missing scripts first.
After you select one or more scripts, the selection toolbar shows the compatible bulk actions:
| Action | When available |
|---|---|
| Assign Collections | Always (opens a dialog to check/uncheck collections) |
| Remove from {name} | Inside a collection view (removes selected scripts from that collection) |
| Move to Team | All selected are personal & owned by you |
| Move to Personal | All selected are team & owned by you |
| Move to Trash | All selected are owned by you |
Actions only appear when every selected script supports that operation. Partial failures show a count (e.g., "8 of 10 completed").
Bulk actions require a network connection. Large operations run in safe batches and keep visible progress until the local library has reconciled with the completed changes.
Collections
Scripts can belong to multiple collections. Drag scripts within a collection to reorder them.
When assigning collections for multiple selected scripts, checkboxes may show a dash (−) instead of a checkmark. This means some (but not all) selected scripts are in that collection. Checking the dash adds the missing scripts; unchecking removes all of them.
Important: Sharing a collection gives the recipient access to all current and future scripts in it. Deleting a collection does NOT delete the scripts inside it.
Select Multiple Collections
From the collections list page, you can select and bulk-delete collections using the same controls as script selection: click Select in the toolbar, marquee-drag on empty space, Shift+Click for ranges, or Cmd/Ctrl+A for all.
Collections are permanently deleted. There is no trash. Scripts inside deleted collections are NOT affected.
Trash
Deleting a script moves it to Trash rather than permanently deleting it. Click Trash in the sidebar to view, restore, or permanently delete trashed scripts.
You can also drag a script card onto the Trash item in the sidebar. In organization workspaces, personal and team trash are separate. The wrong trash bin greys out instantly when you start dragging.
Only the script owner can move a script to trash. Non-owners see the action greyed out in the menu.
Owner Visibility in Team Workspaces
Team scripts you don't own show the owner's name on the card ("by Michael") and at the top of the ⋮ menu with their avatar. Move and Delete actions are always visible in the menu but disabled for non-owners. Click the owner header to see why.