Free Video Preview Links: Review JSON Videos Before You Render

A final video render is the wrong place to discover a clipped headline, an expired image URL, or a scene that moves too quickly. A preview should come earlier, while the JSON is still easy to change.

RenderingVideo provides a public preview flow for that exact stage. You can submit a valid video schema, receive a browser-ready link, and share it with a teammate or client. The public preview endpoint does not require an account or API key, does not consume render credits, and normally keeps the link available for seven days.

What a preview link represents

A preview is a temporary, interactive rendering of the schema you submitted. It is useful for checking composition, timing, typography, animations, and remote assets. It is not a downloadable MP4 and should not be treated as permanent storage.

That distinction keeps the review loop fast:

1. Generate or edit a JSON schema.
2. Submit it to the public preview endpoint.
3. Open or share the returned viewer link.
4. Revise the JSON and create another preview.
5. Convert the approved version into a permanent task when you are ready to render.

Create a public preview

Send the complete schema directly to the video service. Do not wrap it in another config object.

curl -X POST https://video.renderingvideo.com/api/preview \
  -H "Content-Type: application/json" \
  --data-binary @video.json

A successful response includes a temporary ID and one or more URLs. Use the returned viewerUrl when available, then fall back to previewUrl, url, or playerUrl. Preserve the server's expiresIn value instead of calculating an expiry yourself.

What to review before final rendering

A useful review is more than pressing play once. Check the output against a short, repeatable list:

• Safe areas: titles and captions stay readable on the target aspect ratio.
• Timing: viewers have enough time to read each message.
• Assets: images, fonts, videos, audio, and subtitle data load from public URLs.
• Motion: entrances support the message and do not compete with it.
• Contrast: text remains legible over every background frame.
• End state: the final call to action remains visible long enough.

For data-driven work, also test unusually long names, missing optional fields, and extreme numeric values. A template that works with ideal sample data can still fail with real input.

Preview links in team workflows

Temporary links are especially useful at handoff points. A developer can attach a preview to a pull request. An AI agent can produce a schema and return the link for human review. A marketing team can approve the words and pacing before a backend starts a paid render.

Keep the JSON beside the link. The link shows the result; the JSON remains the editable source of truth.

When to move to a permanent task

Create a permanent task after the creative review is complete and the assets are stable. Authenticated API users can create a task from the schema or convert a temporary preview, then start the render separately. This separation lets your product validate first and spend credits only after approval.

Use the Playground to edit real examples and generate a shareable preview, or read the preview and API documentation for the full response fields.