Paste the public URL
Vidily reads the page and collects the product language, brand cues, and available visual proof.
URL to video generator
Paste a URL. Review the story. Export the product video.
A linear, self-serve workflow for SaaS founders who already have a launch page and need a clear video without assembling prompts, TTS, screenshots, Remotion code, and QA by hand.
Generated from palettely.app
Judge the output, not the prompt.
This 39-second launch video was built from the live product page, editor captures, a five-scene storyboard, and one brand system. Vidily turns that production discipline into a repeatable workflow.
- Real product interface
- Natural English voiceover
- Readable captions
- Render and audio QA
Why this workflow exists
A URL is a strong input only when the output remains accountable.
Vidily shows the story and claims before rendering, keeps the real interface visible, and reports failures instead of hiding them behind a generic generation spinner.
- A clear fallback when a URL is private, blocked, or too sparse to analyze.
- Five editable scenes rather than an opaque one-click generation result.
- Visible render stages for capture, voice, video, QA, and upload.
- Failed internal renders release the reserved Export Credit.
Four deliberate steps
A launch pipeline, not a blank editor.
Confirm the story
Review five focused scenes and edit the hook, product promise, proof, outcome, and CTA.
Add real screenshots
Use captured public-page visuals or upload up to three product screenshots when the proof lives behind login.
Render the export
Vidily generates voiceover, motion, captions, and a QA-checked 1080p MP4 from the approved storyboard.
Questions before you render
Which URLs work best?
Public product or feature pages with a clear title, short value proposition, and visible product images work best. Login walls and highly client-rendered apps may need manual screenshots.
Is the generation fully automatic?
The extraction and draft are automatic, but approval is deliberate. You review the five scenes because a commercial video should not publish unchecked claims.
Can Vidily use any topic or article URL?
The MVP is tuned for public SaaS product pages. General articles, news, faceless channels, and arbitrary topics are outside the first recipe.
Why is the output fixed to 16:9?
Constraining the first recipe improves layout reliability and QA. Additional aspect ratios should be added only after the core export is consistently commercial quality.
Your public page is enough to start.
Generate the storyboard, inspect every claim, then decide if the clean 1080p export is worth an Export Credit.