Turn a story you wrote, or one you have the rights to use, into a vertical video with a narrator, atmospheric footage and captions on screen. Write the script with a language model, voice it with a text-to-speech model, generate clips for the mood, and check the captions against a transcript.
Story-time videos follow one simple recipe: a calm voice tells a story while moody footage plays underneath and the words appear on screen. None of it needs a camera, a microphone or a face. You can write the script with a language model, voice it with a text-to-speech model, generate vertical clips that match the mood and check the captions against a transcript, all from one workspace.
The format asks for very little from the picture. The story carries the video, and the footage only has to set a mood: a rainy window, an empty hallway, a car on a night road. That is exactly the kind of loose, atmospheric shot that video models handle well, because nobody checks it for a perfect face or a readable sign. A faceless format also sidesteps the hardest thing to get right in generated video, which is a stable human character from one shot to the next.
The other half is audio. A narrator used to mean a microphone, a quiet room and a lot of retakes. Now a text-to-speech model reads the script in a chosen voice and tone in seconds, so rewriting a line costs you a re-run and not a recording session.
Picasso IA puts every step in one place: language models for the script, text-to-speech for the voice, video models for the clips and speech-to-text for the check. The toolkit runs all of them, and the full catalog lists 502 models if you want to compare options. New accounts get free credits, enough to try one short story end to end before you decide anything else.
Not every story wants the same treatment. A tense confession and a funny office mix-up need different pacing, different voices and different footage. Decide the genre first, then choose the voice and the visual direction that fit it.
| Story type | Voice direction | Visual direction | Pacing note |
|---|---|---|---|
| Tense confession | Low, steady, a little hushed | Dim rooms, rain, slow push-ins | Let pauses land between revelations |
| Petty revenge | Dry and amused | Clean everyday settings, quick cuts | Keep sentences short and punchy |
| Mystery or creepy | Quiet, slower than normal | Empty streets, fog, flickering light | Hold shots longer than you think |
| Awkward or funny | Light, conversational | Bright interiors, simple props | Cut right after the punchline |
| Wholesome | Warm and unhurried | Golden light, soft focus, nature | Slow, with room to breathe |
Two details save a lot of time. First, never put people in the footage when you can avoid it: objects, places and weather are easier to generate and cannot turn into the wrong face halfway through. Second, write the visual direction as its own line in the script, next to each paragraph, so you generate the right clip for each beat instead of improvising later. If you need more footage than you can generate, the page on AI B-roll covers building a bank of mood clips you can reuse.
This is the whole pipeline in order. It assumes you already have a story you wrote or hold the rights to, and about an hour for the first one.
The first pass will feel rough, and that is normal. Most of the polish comes from the second voice take and the shot you regenerate because it did not match the paragraph.
A story that reads well on a page often sounds stiff aloud. Long sentences with three clauses are fine for reading and tiring to hear, and a text-to-speech model will deliver them faithfully, including the monotone. Rewrite for the ear: short sentences, one idea each, the surprise at the end of the sentence rather than the middle.
Read the script aloud once before generating anything. Wherever you run out of breath or trip over a phrase, the voice model will do the same, and no voice setting fixes a sentence that is hard to say.
Voice models also respond to direction. Gemini 3.1 Flash TTS accepts a plain-language style instruction, such as telling it to speak slowly and quietly, plus tags like [whispering] inside the text. ElevenLabs v3 offers stability and style controls and a set of named voices. Use them to keep the delivery consistent across the story, and resist stacking effects: a narrator who whispers, laughs and shouts in the same minute sounds like a demo, not a storyteller.
The same goes for the first line. Viewers decide in a moment whether to stay, so open with the situation or the question, not with background. If you are building a whole channel around this format, the page on faceless YouTube videos covers the repeatable parts, and the notes on AI voiceover go deeper on choosing a voice.
This is the part that decides whether the format is worth doing at all. Public posts on a forum belong to the people who wrote them, and being visible to everyone does not make them free to reuse. Copying someone else's post, then narrating it over your own footage, takes a story that is not yours and puts your channel's name on it. Platforms can remove such videos, and the author can object.
There are plenty of honest sources. Write your own stories, fictional or based on your life. Adapt an idea but tell it in your own words and with your own plot, so the result is a different story and not a paraphrase. Work with writers who give you written permission, or use text that is clearly in the public domain or published under a license that allows reuse, and keep a note of where each one came from.
Keep people out of it as well. Names, usernames and identifying details of real people in a personal story should be changed or removed, and any character that appears on screen should be fictional, never a real, identifiable person. Check each platform's current rules on reused content and on disclosing AI-generated media before you publish, because those rules change.
Knowing the limits saves a wasted evening. These are the places where this workflow stops being useful or needs a human hand:
None of this makes the format unusable. It means the editing pass is the real work, and the generation steps are the fast part.
New Picasso IA accounts get free credits, which is enough to run a short story through each step: a script, a voiceover, a few clips and a transcript. Generation costs credits, and the amount depends on the model and the settings, so a longer video with more clips costs more. Current plans are listed on the pricing page, which is the only place worth trusting for numbers.
Not without permission. A post belongs to its author, and posting publicly does not make it free to copy into a video. Use stories you wrote, stories whose author gave you written permission, or text with a license or public-domain status that clearly allows reuse. Taking a post and narrating it as it is can get the video removed and the channel flagged, so keep a record of where every story came from.
Two good starting points are elevenlabs/v3 and google/gemini-3.1-flash-tts, and both are in the catalog under text-to-speech. ElevenLabs v3 has a set of named voices with stability and style controls. Gemini 3.1 Flash TTS accepts a plain-language style instruction and expression tags such as [whispering]. Run the same paragraph through both and choose the voice you could listen to for two minutes.
kwaivgi/kling-v3-video and bytedance/seedance-2.5 both support a 9:16 aspect ratio. Kling v3 can make clips up to 15 seconds and can script several shots in one generation, while Seedance 2.5 can make clips up to 30 seconds and can produce audio with the picture. For a narrated story, turn the built-in audio off or lower it, so the voiceover stays the main sound.
Send the finished voiceover to a speech-to-text model, such as openai/gpt-4o-transcribe, and compare the transcript with your script. Then split the text into short caption lines and time them in your video editor or a subtitle tool. If you want a dedicated walkthrough, the page on automatic video subtitles covers that part in more detail. Always read the captions once, since names and slang are where transcripts slip.
Yes, within the limits of the models. Gemini 3.1 Flash TTS lists more than 70 language codes, and ElevenLabs v3 takes a language code too. Write or translate the script first, have a native speaker check it if you can, then voice it in the matching language. Captions follow the same logic: transcribe the audio in the same language so the text matches what is said.
There is no rule to quote, and the right length depends on the story and the platform. A tight story told in short sentences can work in a minute or so, while a slower one needs more time. Let the script decide, cut anything that repeats itself, and check the platform's current limits for vertical video before you plan around a length.
Only your own, or someone who has clearly agreed. Do not clone or imitate a real, identifiable person without their consent, and do not put one on screen as a character. Use the stock voices the models provide, or your own recording, and keep any on-screen figures fictional. That rule also keeps you clear of most platform and legal problems.
Many platforms ask creators to label realistic AI-generated content, and the rules are updated from time to time, so read the current policy of each platform you post to. Atmospheric clips and a synthetic narrator are the kind of thing those rules tend to cover. When in doubt, add a short line in the description saying the voice and footage were generated.
Usually the script is the cause, not the voice. Long sentences, no pauses and no change in rhythm make any model sound monotone. Shorten the sentences, put the key line at the end of a sentence and add punctuation where a person would pause. After that, change one setting at a time, such as the style or the tone instruction, and compare the results on the same paragraph.
Your story is the part no model can supply. Open the Picasso IA toolkit, paste the first paragraph and listen to how it sounds in two different voices.
Choose your language
