Create the footage.
Speaking UGC, cinematic scenes, product shots and B-roll. Use characters and image references to guide each shot.
Video · Images · ReferencesYOUR IDEAS. YOUR AGENTS. ONE STUDIO.
A video studio for
you and your agents.
Generate UGC, cinematic clips, images and sound.
Edit by hand or let your agent build the timeline.
Render it all in one cloud workspace.
In your browser. In your agent.
Codex
Cursor
Claudeand more
CursorClaudeand moreEdit preview
Play the cut. Drag a caption. Make it yours.
00:00.000:01.000:02.000:03.000:04.000:05.000:06.0
No narration attached
The actual Studio player, timeline and caption controls. Try an edit right here.
MORE THAN A VIDEO GENERATOR
From the first idea
to the final cut.
Start from scratch or use what you already have.
Keep the whole production in one place.
Give it a soundtrack.
Bring a recording or generate dialogue, music and sound effects. Place each on its own track and shape the mix.
Voice · Music · Sound effectsMake the edit yours.
Ask for a change at any timestamp. Or open the canvas, trim a clip, move a caption and refine it yourself.
Chat · Canvas · TimelineSTART WITH Your idea or narration + Visual references + An optional example video
Make every shot earn its place.
Use this MP3 as the final narration. Build a portrait 9:16, 30 fps edit with product close-ups and 3D explanatory B-roll. Match each visual to the words. Generate every shot in portrait and add short, bold captions. Use the example video for pacing, not as footage.
Example request · no render is started
WHAT COMES BACK
- A cut plan timed to the narration
- New shots composed in the project’s format
- Video, audio and caption tracks ready to edit
Then keep directing.
“At 8 seconds, replace that shot with a product close-up.”
Bring a voiceover, generate one, or make a silent film. The format stays consistent from source generation to export.
LESS HANDOFF. MORE MAKING.
The conversation
becomes the cut.
Use Rend’s built-in agent or connect your own. You direct the work and keep control of the result.
- 01
Bring the idea and references.
A prompt, your footage, an MP3, or a few images. Choose your format and frame rate before the shots are made.
- 02
Build the picture and sound.
Generate what’s missing. Keep what works. If you’re starting with narration, its measured timing guides the cut.
- 03
Refine it together.
“Replace the shot at 8 seconds.” “Give this caption more room.” Chat and Studio update the same project.
- 04
Render the version you want.
Export an MP4 when you’re ready. Keep your sources and earlier versions, so the next edit starts ahead.
One composition. Every track.JSON
{
"format": { "ratio": "9:16", "fps": 30 },
"video": ["opening", "product", "close"],
"audio": ["voice", "music", "sound-fx"],
"captions": {
"font": "Liberation Sans",
"color": "#ffffff"
}
}Your agent edits the document.
You see the picture change in Studio.
ONE WORKSPACE. CLOUD COMPUTE.
Your laptop can
take a break.
Generation, media processing and exports run in the cloud. Your project stays available, and submitted jobs keep going when you close the browser.
Independent renders can run together. Revisions reuse the media you keep. You don’t need to manage a GPU to make the next cut.
Make something in StudioFOR YOUR AGENTS, TOO
The tools behind
the timeline.
Give your agent Rend’s generation, media and editing tools through MCP. It works headlessly; you follow the same project in Studio.
The composition is structured JSON: clips, layers, audio, captions and export settings. Your agent edits the document. Studio brings it to life.
Codex / Cursor / Claude / and more
REMOTE MCP Beta
Connect to your cloud workspace.
Add Rend in a client that supports Streamable HTTP.
https://rend.ai/api/mcpNo Desktop app or local GPU required.
- Use your allowlisted Rend account.
- Add your personal token in the client’s credential settings.
- Ask your agent to create or open a project.
Personal bearer-token beta. OAuth onboarding isn’t available yet. A cloud bridge is also available for clients using stdio.
Read the connection guideA few things
to know.
Start simply. Go deeper when you need to.
Do I need the desktop app or my own GPU?
No. Studio runs in your browser, and the remote MCP connects your agent to Rend’s cloud. Generation and exports run on cloud compute. The older desktop connector is still available for local workflows.
Can I bring my own videos, images and audio?
Yes. Upload media or import a direct HTTPS media URL. Chat attachments work when your client makes the file available to the agent. Use your own MP3, generate a voiceover, or make a video without dialogue.
Can I edit it myself?
Yes. Trim, move and split clips, adjust layers, and edit caption words, timing and appearance in Studio. Your agent works with the same composition, so you can move between chat and the canvas. Export again to include those changes in your MP4.
What happens when I close the browser?
Submitted cloud jobs continue in the background. Return to Studio to find their progress and results. In an external MCP client, your agent checks the job status; a finished render does not automatically wake every chat client.
Can I connect my agent today?
The remote MCP beta currently requires an allowlisted Rend account and a personal bearer token. Use a client with Streamable HTTP support, or the supplied cloud bridge for Codex, Cursor and Claude Desktop. OAuth setup is not available yet.
Does every revision regenerate everything?
No. Keep the source clips you like and change only what needs work. New footage requires generation. Cuts, caption changes and many audio edits reuse your existing media, then render a new export. Your earlier exports remain available.
FROM “WHAT IF” TO PLAY.