OpenPostBrowser support and recovery
Understand device limits and recover projects, sources, or exports.
Supported browser
Use a current desktop version of Chrome or Edge. The full editor depends on browser support for local file access, media codecs, workers, graphics, and origin-private storage.
Codec, WebGPU, screen capture, hardware acceleration, and file streaming vary by browser, operating system, and device. Video Editor checks the operation you selected and explains an unavailable option. A WebM download may be available when this device cannot encode the selected MP4 settings.
Editing, rendering, and transcription run on your device. OpenPost does not provide a server render or server transcription fallback. Local models can use hundreds of megabytes or more. Models shows their stored size and lets you remove them.
A source is missing
Reconnect the original linked file or local project folder. Cloud projects can download originals that were saved as Project Assets. A compatibility proxy or preview cache is not a replacement for the original during final export.
A local project will not open
Choose the same project folder again when the browser asks for access. Confirm that its project and media files have not been moved separately. Clearing browser data can remove remembered folder permission, even when the files are intact.
A cloud project needs attention
Open History and review its conflict copy. Keep the revision you intend to continue. Restoring a revision creates a new current revision instead of deleting later history.
An export stopped
Keep the tab open while rendering. After a reload, check Exports for the saved job and retry it. If the readiness check reports a missing source or unsupported format, fix that exact item before starting another render.
Recording was interrupted
Return to Recorder and use the recovery result it offers. Keep any verified source tracks, then add or download them. Do not clear site data while recovery files are still needed.