Write in any editor. Upload. Generate.
Levizr's file upload feature lets you bring your TTS script from any text editor — Notepad, Obsidian, VS Code, or any tool that exports plain text — directly into the Studio. Emotion tags in the file are auto-recognised. No copy-paste errors. No reformatting.
Why use file upload instead of typing?
The Levizr Studio editor is excellent for short scripts and quick generations. But for creators who work with longer content, pre-written scripts, or high-volume production workflows, file upload is a much faster and more reliable input method.
Skip the copy-paste for long scripts
For scripts longer than a few paragraphs, copying and pasting from an external document introduces formatting errors, unwanted whitespace, and invisible characters that can affect how the neural model reads your text. Uploading directly from a .txt file avoids all of that — the content loads clean every time.
Preserve your existing workflow
Many content creators write TTS scripts in Notepad, Obsidian, Notion exports, or script-writing tools that export to plain text. Levizr's file upload lets you stay in whichever writing tool you prefer and simply upload the final file — no need to change how you draft your scripts.
Faster turnaround on batch content
If you produce high volumes of TTS content — multiple podcast episodes, a series of product descriptions, training module narrations — uploading pre-written .txt files is dramatically faster than typing or pasting each one individually into the editor.
Supports emotion tags written ahead of time
You can write emotion tags like [excited] or [whisper] directly in your .txt file before uploading. When the file loads into the Levizr editor, those tags are automatically parsed and rendered as visual chips — exactly as if you had typed them manually in the Studio.
How file upload works in Levizr Studio
The upload flow is designed to be a zero-friction single action — one click opens the file picker and the content is in the editor immediately.
Write your script as a .txt file
Create your script in any text editor — Notepad, TextEdit, VS Code, Obsidian, Notion export, or any tool that saves as plain text. Include emotion tags like [giggle] or [whisper] wherever you want them. Save the file with a .txt extension.
Click the Upload icon in the Studio
In the Levizr Studio editor, look for the upload icon (arrow pointing up) in the floating toolbar at the bottom-right of the text area. Clicking it opens a standard file picker. Only .txt files are accepted — other formats will not load.
File loads into the editor instantly
Your script content appears in the editor immediately. Emotion tags in the file are parsed and converted into visual chip elements. The word count updates automatically. You can edit the loaded text normally before generating.
Generate as normal
Once your script is loaded, proceed as you would with any manually typed text. Select your voice, add a system prompt if needed, and hit Generate Speech. The upload was just the input method — everything else works identically.
Best practices for file uploads
Following these guidelines will ensure your file loads cleanly, emotion tags parse correctly, and your generation produces the best possible audio output.
Use UTF-8 encoding
Save your .txt file with UTF-8 encoding to ensure non-English characters — Hindi, Arabic, Japanese, and other scripts — load correctly into the Levizr editor without garbled characters.
In Notepad: File → Save As → Encoding: UTF-8
Keep sentences on separate lines for readability
While not required, formatting your script with one sentence per line makes it easier to scan and edit after it loads in the Studio. The neural model reads the text as a continuous block regardless of line breaks.
This is a stylistic preference, not a technical requirement
Write emotion tags in square brackets
Make sure emotion tags follow the [tag] format with no spaces inside the brackets. Tags written as [ excited ] or [Excited] with capitals will still be parsed, but lowercase with no spaces is the most reliable format.
Correct: [excited] — Incorrect: [ excited ] or [EXCITED]
Stay within the 1,000-word limit
Levizr processes up to 1,000 words per generation. If your .txt file is longer, the word count indicator in the Studio will flag the excess and prevent generation until you shorten the text.
For longer content, split into multiple .txt files and generate in segments
Works with any tool that exports plain text
Frequently Asked Questions
What file types can I upload to Levizr TTS?
Levizr currently supports .txt (plain text) file uploads. Other formats like .docx, .pdf, or .rtf are not supported at this time. To use content from a Word document or PDF, export it as a plain text file first.
Is there a file size limit for uploads?
There is no explicit file size limit, but the practical limit is the 1,000-word generation cap. Files significantly longer than 1,000 words will load but the excess content will be flagged by the word count indicator and generation will be blocked until the text is shortened.
Will emotion tags in my .txt file be recognised automatically?
Yes. Emotion tags written as [tagname] in your .txt file are automatically parsed when the file loads into the Studio editor. They are converted into visual chip elements and treated exactly like tags you typed manually. This means you can prepare fully tagged scripts in your preferred text editor before uploading.
Can I edit the uploaded text after it loads?
Yes. The uploaded text is fully editable once it appears in the Studio editor. You can add, remove, or modify text and emotion tags normally. The upload is just an input method — it does not lock the content.
Does uploading a file overwrite text I already typed in the editor?
Yes. Uploading a file replaces the current content of the editor with the file content. If you have unstyled text already in the editor that you want to keep, paste it or save it elsewhere before uploading a new file.
Does the uploaded content get saved between sessions?
Yes. Levizr saves the current editor content to localStorage automatically. If you upload a file and then close the tab, the content will be restored on your next visit. Note: localStorage is device and browser specific.