How DepCut Renders Your Export Right in the Browser

When you export a cloud project, DepCut can do the rendering on your own computer, in the tab you are already using. The cut does not travel to a render queue first, and the file comes from the same drawing code that produced your preview.

Why the file matches the preview

The editor draws your cut live to show the preview. At any moment, what appears on screen is worked out from your project and a point in time. An export asks the same question for every frame, jumping straight to each moment in turn. Both the preview and the export go through one compositor, so the exported MP4 shows what you watched.

What happens after you press Export video

1. DepCut checks that the tab can carry the render. The next section covers the two checks.
2. It reserves the file name and the destination before drawing a frame. A refusal arrives at the start of the export and costs you no render time.
3. The tab draws each frame, mixes the audio and writes an MP4 to scratch storage in the browser. The file streams to that storage, so a long render does not have to fit in memory.
4. The finished file uploads to the project's storage. The last stretch of the progress bar is this upload.
5. The export shows Ready in the exports card and joins the Exports list in the Media tab.

While the render runs, its row in the card reads Rendering… with a percentage. Pressing Stop export ends it and starts nothing else.

What the tab needs

DepCut probes the browser for every export, since the answer depends on the browser and on the preset you chose:

• Scratch storage in the browser's own file system, where the render writes its file.
• A video encoder in the browser that can handle the frame size you picked.

A browser with both, and a cut of 10 minutes or less at no more than 4K with no neon caption style, runs the render itself. A project stored on your Mac renders in the DepCut Mac app, using its bundled ffmpeg.

When the tab cannot do the job

If any check fails, the export goes to DepCut's hosted renderer, and you do not have to do anything. The same hand-off happens when a browser render fails partway, or when the tab stops making progress. A tab that the system suspends in the background, such as a phone with a locked screen, can stall without ever raising an error, so DepCut watches for progress and moves the export to the hosted renderer after a stretch of silence.

In the card, you see the row change from Rendering… to Preparing… and then follow the hosted export. You see an error only when the hosted renderer fails too.

Tips for smooth renders

• Keep the tab open until the row shows Ready.
• Pick the preset for the job. The encoder probe uses the frame size of the preset you chose, and a Draft · 720p frame is smaller than a Best · 1080p one.
• Wait for imports to finish uploading. The render reads the saved project, and the Export button stays disabled until every import has landed.

Watch a render

Export a short cloud project from DepCut and watch the card switch from Rendering… to Ready.