Browse documentation
← ReferenceFind another guide
Reference

Browser, device, and permission checks

Your browser must read your media, play the sequence, preserve your work, and download the result. Check these operations on the device and browser profile you intend to use.

On this page
What this guide helps you do

Choose a working setup, understand feature availability, and check a small project before a longer session.

Before you begin

  • Preserve any useful unsaved work before changing browsers, devices, or browser settings.
  • Use the correct account and workspace, with original media available.
  • Prepare a small sample using the same kinds of image, video, and audio files as your intended project.

Understand the browser and screen boundary

Desktop Chrome is the current automated Editor test target. This does not establish complete compatibility for every feature, browser version, or device. Use the checks below for your files and workflow.

Editor requires a viewport at least 320 pixels wide. Below that, Wider screen required offers a return to Workspace. Widen the window or use another device.

Minimum width is a layout requirement. It does not confirm recording, media decoding, storage, or a fully verified mobile editing workflow. On compact screens, check object selection and controls before detailed work.

Check each requirement separately instead of treating page access as proof that the full workflow is ready.
AreaWhat must workWhat to verify
Editing layoutEnough viewport width to open Editor and reach its controls.The canvas, timeline, selected object, and actions remain usable.
Imported mediaThe browser can read the selected image, video, or audio.The source loads, its duration is valid, and playback works.
RecordingThe feature is available, the browser supports it, and device access is allowed.The intended microphone or camera can be enabled and a short take can be reviewed.
This device savingBrowser storage accepts the project or draft write.A successful save status appears and the expected local project can be reopened.
Cloud workThe account has access and the save or load request succeeds.The correct project opens and its cloud save is confirmed.
Finished outputRendering completes and the browser saves the downloaded file.The file is present on the device and opens outside Editor.

Check a small project before a long session

One working image does not demonstrate support for a different video encoding. Use representative files and check the complete sample before a long editing session.

  1. Open the right workspace

    Confirm the account, project, and save location. Use a small test project or preserve the current project before changing it.

  2. Add representative media

    Import representative files, add them to the timeline, and move the playhead inside their time ranges. Confirm the expected picture and sound.

  3. Try the controls you need

    Make a small edit, such as adjusting text or timing. Check that selection, scrolling, and the relevant panel work at the window size you will use.

  4. Confirm saving

    Use the intended local or cloud save and wait for success. Reopen only after preserving the work, then check that the recent change and media are present.

  5. Check an output

    When export is available, render a short sample, download it, and inspect it outside Editor. A successful source preview alone does not confirm the full export path.

Check camera and microphone access when recording is offered

Check the application’s availability message first. Recording needs both an available feature and browser support. Granting permission does not enable an unavailable tool.

Camera and microphone access require HTTPS and a supported browser. When you choose to enable a device, allow access for the intended ZOVOZ site in both browser and system privacy settings. Select the intended input and review a short take before recording longer content.

If microphone recording is unavailable, upload an existing voice-over. The browser must also create a supported recording format; an available microphone alone does not confirm that recording can finish.

Use the device error to choose the next action.
Message or symptomNext action
Access was blockedReview the site's browser permission and system privacy setting, then retry the requested device.
No matching camera or microphoneConnect or choose an available input device before retrying.
Device is busyClose the other application using that input, then enable it again.
Recording is unavailable in this browserUse an existing recording through the supported upload workflow.

Keep local work tied to the correct browser profile

Local and This device projects use the current browser’s stored data. Another browser, profile, or device does not automatically contain those copies. Reopen local projects in the same working profile.

Look for a successful save status rather than assuming that visible content is saved. If browser storage refuses a write, keep the working tab open and follow the message before replacing or leaving the project.

Preserve work before clearing site data or switching environments. Keep original media and appropriate backups. A Creator draft restores Creator content, not later Editor timeline edits. Follow the saving and recovery guides for your copy.

Separate playback, rendering, and downloading

Check source types and sizes in the format reference. If the browser cannot read a video or its metadata times out, retain the original and try a known-working file of an accepted type.

Inspect the editable timeline, a rendered sequence preview, and the finished export separately. They serve different purposes. For an export, wait until the result is ready, choose Download file, and check the browser's download list and destination folder.

Follow any instruction to keep the tab open during rendering. Save before leaving or reloading. If downloading fails, keep the ready-result message and exact error for troubleshooting.

Get help with a repeatable browser problem

Contact support with the browser name and version, operating system, device, approximate window size, and exact error. Include the file type and size, whether the project is local or cloud, and the action that fails.

Explain what still works, such as source playback, saving, or downloading. Keep any working tab and original files available while the problem is investigated; avoid clearing the only remaining device copy as a first troubleshooting step.

Check your result

  • Editor opens at a usable window size and the required controls can be reached.
  • Representative source media loads and plays correctly.
  • Any required recording feature and device permissions have been checked.
  • The intended local or cloud save succeeds and can be reopened.
  • A short finished output can be downloaded and inspected.
Still have a question?

Tell us what you were trying to do and the message you saw.

Contact support
Browser and Device Compatibility Checks | ZOVOZ