Rendering guide
Prepare media and monitor cloud render jobs.
Media access
Cloud render workers cannot read browser blob: URLs or files that exist only on a user's device. Upload each media file before you submit the render.
Use one of these sources:
- A public HTTPS URL
- A signed HTTPS URL that stays valid for the full render
- A URL from your own authenticated media proxy
For private storage, create signed URLs on your server. Do not put storage credentials in the render payload.
Create signed URLs only when you prepare the cloud render payload. Keep the editor's local or blob: URL unchanged so browser editing continues to work.
The signed URL must remain valid while the job waits, renders, and stores the output. Test the URL in a private browser window before you start the render.
Check these properties for each media URL:
- The URL uses HTTPS.
- The response returns the media file, not an HTML sign-in page.
- Redirects do not require browser cookies.
- The content type matches the file.
- The URL stays valid for the full job.
Job progress
After submission, the API returns a render identifier. Use this identifier when you request progress.
A progress response has one of these states:
progress: The render is running.done: The output is ready.error: The render failed and includes an error message.
The RVE Portal also shows the job status, video settings, usage, output size, and failure details.
Store the render identifier with your own job record. It is the main reference for progress checks, support, and failure investigation.
Output downloads
Use the output URL returned by the completed job. If you want a browser download, fetch the file and create a local object URL before you trigger the download. Opening the remote URL directly can navigate away from your application.
Move important outputs to your own storage before the Cloud Rendering retention period ends. The beta retention policy can change while RVE tests real usage. Confirm the current policy for your account before you depend on long-term output storage.
Long videos
Test long projects with real customer media before you increase usage. Check signed URL expiry, render duration, output size, and browser download behaviour.
Region and customer data
RVE runs each render in the cloud region selected for the customer account. Do not send personal data in source labels or external references. Use internal identifiers that your application can resolve.
Large batches
Use a queue and bounded concurrency for large batches. Do not start an unlimited number of requests with one Promise.all call. See Batch Rendering and AI Agents.