Make the next revision easier to make.

Start with a saved version.

Save your video, watch its preview and completed export, then open Feedback on saved versions in the studio. Choose the version you are discussing. The editor’s current draft may contain changes that are not in that saved revision.

If a connection or server error leaves a save uncertain, keep the editor open and the edits unchanged, then choose Save video again. The same attempt can recover its saved result. Check the returned version before editing further. Reloading clears the editor’s retry identity; after a reload, check Your videos and version history before creating another copy.

Each note stays attached to its version. When someone saves a new revision, earlier notes remain available under Feedback version. Choosing a feedback version changes the notes you see; use Version history to load an earlier composition for visual review. Loading history pauses autosave, so reviewing an old version does not immediately replace the current one.

Compare before loading an older version.

Open Compare saved versions and choose Compare against saved version. The comparison shows that saved document beside your current draft, including unsaved changes. It identifies changed scene wording, order and settings, audio and effects, caption appearance and complete caption tracks. Open each track's word times when you need to inspect them.

This control leaves your draft unchanged. Changing the comparison version, editing the draft or saving another version updates the comparison without loading the older document. Version history remains the separate control for loading a saved composition into the editor; autosave turns off, and Undo restores your prior draft.

A document comparison does not establish media fidelity, sound quality, an exact export decision or publication. Graphics and different private source references need visual review after loading the version. Correct an invalid current draft before comparing, and review the completed exported file before approving it.

Keep the brief behind the video.

When you apply a storyboard made from a saved brief, Original draft and source retains its selected brief revision alongside the original scene wording. Compare the video against that objective, audience, hook and shot list. Editing the brief later does not silently update existing videos; make and review a new draft when those changes should affect the result. Follow the brief-to-storyboard guide to start from an exact revision.

Describe one useful change.

1. Choose Whole video for a pacing or overall-message note, or select the relevant scene under Note location.
2. State what you observed: “The opening names three problems before showing the product.”
3. Suggest a concrete revision: “Keep the first problem and move the product demonstration into scene two.”
4. Explain the intended result: “That gives a new viewer a reason to keep watching before the details arrive.”
5. Select Add note to version… and check the version number on the button.

Notes are plain text, up to 2,000 characters. They are visible to members of this workspace. Agent-created notes are labelled as such. An unposted draft stays attached to its selected version when a newer video revision is saved, and leaving the editor prompts you to keep or discard that draft.

Close the loop after making the edit.

Save and inspect the revised video, then return to the earlier note and choose Resolve note. Use Reopen note if the issue needs another pass. Resolving a note records its working status; it does not approve the media or publish anything.

If a teammate changes the same note while you are reading it, the studio asks you to refresh instead of silently overwriting their status. Select Refresh feedback, read the current state, and decide whether another change is needed.

Try a different opening without replacing the original.

When you want two alternatives, save your current video and finish any unposted notes, then choose Duplicate video. Give the copy a useful name, such as “Notebook launch — product-first opening”, and select Create separate video. The new video begins at version one.

The copy keeps the saved scenes, media, soundtrack, captions and recorded source context. It reuses the workspace’s private files. Comments, exports, approvals and client preview links stay with the original. Change the copy’s opening or format, inspect its framing and captions, then save, export and review it separately.

For new copies, open Original video and copies to see the original title and saved version used at creation. Follow Open original video to its current revision, or open one of the copies listed on the original. The source version stays the same even when either video changes. Older copies and conflict-recovery saves may not have this link.

While the copy form is open, autosave pauses. Cancel copy returns to the original without creating a video. If you edit the original before submitting, undo those changes or cancel the copy and save them first. A new video uses one of the workspace’s 100 saved-video places; copying does not generate or export media.

Check the export before starting it.

Save the video and choose Check export to see that version’s dimensions, duration, scene count, source-media size and remaining trial attempts. Reused files count once toward the 12 MB source-media limit. The check explains unavailable media or features and exhausted capacity before you deliberately start another export.

The result is a snapshot, not a reservation or a promise about output size or finishing time. Files and limits are checked again when exporting. Use Refresh export check after another job finishes or capacity changes. Paid pricing is not configured. The trial uses one attempt for a new accepted export; retrying its original request confirms the same attempt.

Make a decision on the finished file.

After saving and exporting the current version, choose Review export, then Load exported video. Remixure checks that the file matches the export before making the review controls available. Watch the whole video, including its captions, sound, claims and media rights.

If export confirmation is interrupted, keep the page open and choose Retry same export request. This recovers the original saved version without creating another export attempt. You can keep editing while it is uncertain; a later saved version does not change that request. After reloading or leaving the page, check Exports before starting a new request, because a new request deliberately creates another export.

A verified workspace member can approve that exact export, request changes with a reason, or withdraw an existing approval. Confirm your selected decision and choose Record review decision. The history keeps earlier decisions, and Download latest review receipt saves the version, reviewer, decision and file fingerprint as JSON.

Saving a new version means the previous approval no longer covers the current video. Export and review the new version again. A second export also needs its own approval, even if it came from the same saved version. An approval never posts a video or grants permission to publish it.

If another member changes the review while you are deciding, use Refresh review to read their decision before trying again. Older exports without a file fingerprint remain downloadable; make a fresh export to use the review workflow.

Let a client watch without joining your workspace.

A verified workspace owner or admin can open Client previews, feedback and decisions after loading and watching the current export. Choose an expiry of one hour or one day. Optionally enable Allow guest feedback, then confirm the file can be shared, and select Create client preview.

Copy the preview details before leaving. The separate code is shown only once. Send both the URL and code to the intended reviewer; anyone who has both can watch or keep a copy. The URL alone does not reveal the video. The guest page checks the file and shows its saved version and access expiry, without opening your workspace, source text or feedback history.

Choose Revoke preview to block future access. Saving a newer video version also closes earlier previews. Neither action can remove a copy the recipient already opened or saved. If you enabled feedback, the guest can write a note after the video opens. Their name is optional and unverified. The note is tied to the exact export and version; it is visible to your workspace team, not to other guests. Watching or commenting does not record an approval.

If creation is interrupted, use Recover this link request to retry the same request. A code that was already issued cannot be recovered. Refresh the preview list, revoke the affected link, then deliberately start a new link request. At most three links can be active for a video, with 20 new links per workspace per UTC day. Each link allows 20 file loads per UTC day, subject to shared workspace and service limits.

Open Guest feedback on this export and use Refresh previews, feedback and decisions to read new notes. Notes remain with the original export after revocation or a newer edit. If a guest loses confirmation while sending, Retry same feedback recovers the same receipt without adding a duplicate. The draft stays in the page until it is confirmed or deliberately discarded.

After making and checking the edit, choose Resolve guest note beside the original note. Use Reopen guest note if it needs another pass. The status records who last changed it and stays with the original export. It does not approve a video, send a reply or notify the guest. You can still manage those notes after the link closes.

If a teammate changes the status first, refresh the feedback and read the latest state before deciding again. If the change may have saved but its confirmation was lost, Retry same feedback change recovers that same result. Do not treat an unverified guest name as proof of identity.

For a new guest note, choose Open conversation to read its replies. A verified workspace member can write a response, confirm that the guest should be able to read it, and choose Send reply to guest. The guest can choose Refresh conversation and Send follow-up during the current visit or after reopening it with a saved private conversation key. Other guests need that private key as well as the preview code to read its replies.

Before leaving, the guest can open Return to a conversation, confirm that they will keep the key private, and choose Save private conversation key. On another visit, they open the same preview with its separate code and choose that key file.

The file contains a private conversation reference, not the preview code, note text or unsent drafts. Anyone with both the file and code can act as that guest, so it should not be shared. It cannot reopen an expired, revoked or superseded preview. No email is sent.

Without a saved key, closing or reloading loses access; starting another note switches to its conversation. Older notes without private conversation access stay readable by the team but cannot receive guest-visible replies. New replies require an active preview; the team retains the history after it closes.

If another reply arrives before yours, keep your text and choose Refresh and review this draft again. Read the new message before sending. If a connection error leaves sending uncertain, Retry same reply confirms the original request without adding a second message. Each conversation allows 20 replies in total, with shared daily limits of 100 per link, 200 per workspace and 1,000 across the service.

Each link accepts up to 20 notes and each export up to 100, with shared limits of 100 notes per workspace and 500 across the service per UTC day. A team member or video-write agent can make up to 50 status changes per workspace and UTC day, with 100 changes per note and 1,000 per export. These are capped preview limits. Email notifications are not available yet.

Ask for a guest decision on the exact file.

When creating a new preview, an owner or admin can separately select Allow guest decisions. Existing links stay unchanged. This permission is independent of guest comments. The recipient opens the finished file, watches it and confirms the version before choosing Record decision. They can approve that file, request changes with a note, or withdraw their own earlier decision.

The sender reads Guest decisions on this export, then Decision history for earlier responses. Guest names are unverified; a private recipient key keeps one reviewer’s changes separate from another’s. A guest approval does not replace internal member approval, establish a verified identity or authorize publishing. Decisions remain tied to their original export after the preview closes.

Before leaving, the guest can open Keep or reopen your decision key, confirm that they will keep it private, then save or copy it. Confirm that a downloaded file actually saved. A copied key can be kept in a private JSON file. On another visit, open the same preview with its code, then Choose decision key or use Use a copied decision key and Reopen copied decision key. The key excludes the preview code, notes and drafts; anyone with both the key and code can act as that reviewer. It cannot reopen an expired, revoked or superseded preview.

If confirmation is lost, keep the draft and choose Retry same decision to recover the original request without a duplicate. When another change has already been recorded for the same key, refresh your own history, review it and deliberately confirm a new decision. Unsent notes warn before navigation and block closing the video until sent or discarded.

Each private key allows up to ten recorded changes, within shared limits of 20 decision entries per link, 100 per export, 100 per workspace per UTC day and 500 across the service per UTC day. Comments and decisions have separate limits. No notification or email is sent; the sender must refresh to read new decisions.

Find review updates across your videos.

Open your workspace and check Review updates for notes, decisions and conversation replies from the last 30 days. Choose Refresh review updates to check for changes. The first three appear immediately; More review updates opens additional entries, with up to 90 shown in the app.

Each update names its saved version. Open saved video opens the current editor; select the matching feedback version or export history to read the original response. A later edit does not move earlier decisions onto the new file. Guest identities remain unverified, and their approval does not replace member approval.

Mark current updates seen saves your own seen position through the displayed time, including older entries. Later replies stay new. It does not resolve a note, approve a video or change another member’s status. If confirmation is lost, choose Retry marking updates seen to recover that same request. Email and push alerts are not sent.

Keep the review inside its current limits.

You can also save a PNG cover from the exported video. Capturing a frame is separate from recording a review decision.

Workspace members can leave notes and record decisions; guests can view a deliberately shared export using its URL and separate code. Guests can send feedback only when the sender enables it for their link. A separate sender opt-in allows unverified guest decisions on the exact file; these do not replace verified member approval. Email notifications are not available yet. Agents can read review decisions and preview status, but cannot approve an export or grant guest access. Receipts record a workspace decision; they are not digital signatures or legal certifications.

The current editor shows up to 50 recent saved versions and review decisions. The service allows 50 new notes per author and workspace per UTC day, 200 per version and 1,000 per video. Review decisions have a separate limit of 50 per author and workspace per UTC day and 1,000 per video. Export files are limited to 64 MB.

Start with an editable template, keep recurring footage in your workspace media library, and use the short-form workflow to choose the question each revision should answer.