Recreate the workflow, not the screenshot
A blog player with Recreate is a recipe. A screenshot of a viral clip is a guess. Use /workflows.
A screenshot of a viral clip is a mood board. It tells you the room was warm, the caption was big, the product was in the first frame. It does not tell you the model, the stills, the scene list, the voice line, the duration, or the credit cost. Guessing those from a still is how you spend a day reproducing a vibe and ship a different film.
A blog player with Recreate is a recipe. The clip on this page is the NYC street interview workflow: scenes, prompts, references, model. Recreate clones that object into an account you can run or edit. That is the conversion loop. Workflows is the catalog — seventeen public recipes with every scene unlocked.
Do not reverse-engineer a screenshot when a recipe exists.
A workflow is a file you can run
The public workflows on Versely are not "inspiration." Each one is a complete object:
- ordered scenes with durations
- image prompt and video prompt per scene
- voiceover line when the scene talks
- reference images for the people and products that have to hold
- a named video model
- an estimated credit cost, quoted before you run it
That is why Recreate is not "make something like this." It is "materialise this graph." Recreate a viral template is the agent verb: browse, clone into your account, then run or remix. Cloning is free. Running is priced like the generation it is. You see the cost before anything dispatches.
A screenshot cannot clone. It can only be described, and a description is a new prompt, and a new prompt is a new film. Teams that brief "like this TikTok" are asking for a guess with extra steps.
What Recreate is for on a blog post
Some posts on this site carry a player and a Recreate control. That is not decoration. The VideoObject on the page is the proof; the control is the recipe. If you watch the clip and want the pipeline, you should not have to pause and transcribe the caption.
Use it when:
- The post is arguing a shape (street interview, product comparison, hook-led UGC) and the workflow is that shape, filled in.
- You want the scene list more than you want a new idea. Remix after clone: swap the product stills, keep the cuts.
- You are teaching a client what "this format" means. A cloned workflow is a spec. A screenshot in a Slack thread is not.
Do not use it when you only wanted the hook line. A workflow is a whole film. If the variable you are testing is the first three seconds, generate a hook pack before the video exists is the cheaper object — distinct openings, one body later. Recreating a three-scene interview to get a new first line is using a film to do a pack's job.
Screenshot workflows fail in the same three places
Identity. The person in the viral still is not in your reference pack. Your generate invents a cousin. The workflow already named Riley and Kai and attached their stills.
Model. The screenshot does not say Seedance versus Veo versus Kling. People paste a cinematic still into a talking-head model, or a talking shot into a silent beauty model. The workflow named the model because the model is the look.
Structure. A 9:16 street interview is timed beats with a mic in frame, not "a woman in New York." Without durations and lines you write a paragraph and get a montage.
| You have | You should | You should not |
|---|---|---|
| A public workflow on this site | Recreate, then swap assets | Rewrites of the prompts from memory |
| A competitor's ad, no recipe | Lock stills, then I2V, new board | One prompt that says "like this" |
| A hook you liked | A hook pack against your offer | Recreating their whole film |
| A series you already ran | Clone your own workflow, new episode | Starting from a screenshot of episode one |
The last row is the one agencies miss. Once a format works, the workflow is the product. Save it. Recreate it. Change the product still. Do not go back to Pinterest.
Recipes versus vibes
"Golden hour, candid, handheld" will produce a clip. It will not produce this clip, or the next ten that have to sit next to it. Recipes transfer: a page can show the film, name the cost, and hand you the graph. Brief a human with the workflow URL. Brief the agent with "recreate this template and swap in these product photos" — it already knows recreate_public_template.
Seventeen workflows is a set of shapes, not an infinite feed. Pick the shape that matches the buy. Then Recreate. Then stop screenshotting.
FAQ
Is Recreate the same as downloading the MP4 and uploading it again?
No. Downloading the MP4 gives you their pixels. Recreate gives you the scene graph — prompts, references, model — as a saved workflow in your account. You need the graph if you want the next episode. You need the MP4 only if you are quoting the film, which you usually are not allowed to do.
Does cloning a workflow spend credits?
No. Clone is free. Credits apply when you run it, at the cost shown before dispatch. Edit prompts and swap assets while it is still a draft if the cloned product is not your product.
What if the viral clip I care about is not in /workflows?
Then you do not have a recipe. Build one: stills first, then I2V or R2V, then save your workflow so the next time is a Recreate. Do not spend a week guessing their model from compression artefacts.
Can I Recreate a blog example that is only a hook clip?
If the post wired Recreate to a hook pack or a workflow, yes — that control is the recipe. If you only have a player and no Recreate, you have a demo, not a graph. Use create a branded hook pack when the object you actually want is openings, not a cloned film.