Scripts travel between people: the presenter sends the draft to a colleague, the marketing copy goes to the founder who’ll read it, the teacher passes the lesson to the substitute who’ll record it. The usual channels — chat screenshots, email attachments, “I’ll paste it in the call” — lose formatting, versions and time.
Script sharing in NanoPrompter is one link: password-protected, expiring automatically in 24 hours, readable on any device. This page explains how to use it and the privacy model behind it.
How it works
- In the editor, choose share. Set a password — something you send through a different channel than the link (message the link, say the password in a call).
- Send the link. The recipient opens it in any browser, types the password, and reads the script with formatting intact: bold highlights, colors, line breaks.
- Forget about cleanup. The shared copy deletes itself after 24 hours. No archive, no version drift, no “which attachment is the final one”.
Why a password AND an expiry
The two mechanisms protect different failures. The password protects the link itself — forwarded by mistake, guessed, pasted in the wrong chat. The expiry protects accumulation: nothing useful remains on a server after the collaboration moment has passed.
For extra-sensitive material, the honest advice is to treat any shared script like a postcard that shreds itself: convenient, protected from casual viewing, not a state secret channel. For virtually all real use — scripts, rundowns, lesson plans, announcement copy — the combination is exactly right-sized.
What recipients can and can’t do
Recipients open the link on a phone, tablet or computer, enter the password, and see the script. From there they can read it on screen, use it in their own teleprompter session, or copy the text into their own editor. They don’t get access to anything else of yours — your other scripts stay in your browser, unreachable from a shared link.
Where teams use it
- Co-hosted recordings: the rundown goes to the second presenter; both read the same lines. See podcast workflows.
- Delegated recording: you wrote it, someone else records it — a colleague, a client, a substitute teacher (teachers).
- Review before shooting: send the script to the approver; they read it as it will scroll, not as a document.
- Multilingual teams: the same script shared with the presenter in each language, one link at a time. The interface supports 9 languages.
Limits, honestly
The link doesn’t update live — if you edit the script, share again to send the new version. And sharing doesn’t sync devices: your scripts live in your browser’s storage, so “continuing on the tablet” means sharing with yourself (a legitimate trick: password you know, 24 hours is plenty, and it deletes itself).
Send the next script as a link
Write it in the editor, click share, set a password, send the link. The colleague reads it in their browser — and tomorrow there’s nothing left to clean up.