Skip to main content
On this page

Planning & Review

Frame.io for Unreal Engine

File review with timecoded comments, version comparison, share links, and supported 3D previews.

It's ideal when rendered video is what gets reviewed, especially if the team already edits in Premiere Pro or After Effects.

What it is

Frame.io is a media review system. Reviewers open shared assets, leave comments on an exact frame or page, draw annotations, group revisions in version stacks, and compare assets in the comparison viewer.

Pause a cinematic at frame 1842 and annotate the doorway where the camera settles late. The editor can open that frame directly from the comment.

The comparison viewer places two versions or unrelated assets side by side. Supported 3D exports, including GLB and USDZ, use rendered turntable previews with comments tied to the viewing angle.

With Unreal Engine

Frame.io can review Unreal cinematics, gameplay captures, images, documents, and supported 3D exports. Reviewers can annotate a camera cut, compare revised renders, or inspect a rendered turntable preview of an exported model.

Where it fits

Strengths

  • Comments and drawings attach to a specific video frame, image, or PDF page.
  • Version stacks keep related revisions available from one asset.
  • Share links support client and stakeholder review outside the production workspace.

Tradeoffs

  • Its 3D viewer uses rendered turntable previews. It doesn't run an Unreal scene or provide free camera navigation.
  • Comment attachments require a Pro plan or higher.
  • Features differ between Frame.io account versions and plans.

Choose it when

  • Rendered video or post-production media is the main review artifact.
  • Editors need timecoded comments and revision comparison close to Adobe tools.
  • Clients need controlled review links without access to the whole production workspace.

Look elsewhere when

  • Reviewers need to run an interactive Unreal build or inspect native .uasset and .umap files.
  • The team needs broad project planning where review feedback becomes project work.

How it works

Frame and range comments
A single-frame comment records its timecode. A range comment covers a section, such as the whole camera move from 00:12 to 00:16. Images and PDFs can carry annotations on the relevant image or page.1
Annotations and attachments
Arrows, boxes, lines, and freehand drawing can be saved with a comment. Adding a file attachment to a comment requires a Pro plan or higher, and non-media attachments do not receive the same preview as supported media.16
Version stacks
Related revisions live in one stack rather than separate folders. Reviewers can open any earlier version from the stack.37
Comparison viewer
Frame.io V4 can compare supported video, image, audio, PDF, and Office assets. Static assets also support Overlay and Pixel Difference views. Overlay requires both assets to have matching dimensions.3
3D turntable previews
Frame.io converts supported self-contained 3D files into turntable previews. Comments record the viewing angle. This viewer plays a rendered turntable rather than letting you navigate the original scene freely.9
Shares and access
Review links expose selected media without giving every reviewer full project access. Link settings control permissions and availability. Project access requests still route through users who have permission to grant access.28

In production

  1. 01

    Upload a review-ready render

    Name the export with its sequence, shot, and revision, such as SQ020_SH040_v07. Check frame rate, resolution, color, and audio before sharing it for review.

  2. 02

    Ask one specific review question

    State whether the review covers animation timing, lighting, the edit, sound, or final approval. Keep unrelated feedback for the appropriate pass.

  3. 03

    Resolve notes against the next revision

    Use timecodes, ranges, drawings, mentions, and tags to classify the feedback. The owner decides which notes enter the next revision and records rejected or superseded direction. Add the next version to the same stack, keep the earlier one available, and compare the changed passage before marking comments resolved.

  4. 04

    Record the accepted revision

    Record the approved version where the team tracks the shot. Include its revision number and review link so the next person can open the accepted file.

Best practices

Validate the export before review
Use stable sequence, shot, and revision names. Play the uploaded file and check frame rate, resolution, color, audio, and duration before sharing it.
Keep revisions in one version stack
Stack related revisions, compare the changed section against the prior version, and confirm the comment target before posting. Record superseded direction so an old note does not return in the next pass.
Test every external share
Set the passphrase, expiration, comment, download, and version-visibility controls for the audience. Open the share outside the project account and verify it exposes only the intended assets.

Gotchas

V4 and Legacy have different features
Some integrations and workflows differ between Frame.io V4 and Legacy. Migrated Legacy review and presentation links cannot be edited, though duplicating one turns it into a V4 share. Confirm the account and share type before documenting a client workflow.24
Shared folders update after the link is sent
A share that contains a folder can expose media added to that folder later. Use a dedicated review folder or share selected assets when future uploads must remain private.2
Comparison comments belong to one side
The comparison viewer asks whether a comment targets the left or right asset. Confirm the active target before writing the note. Overlay also requires both static assets to have matching dimensions.3
Viewer support depends on the media details
A file extension can be accepted while its codec, encoding, or document behavior fails the intended review. Test the actual export preset and review controls before a scheduled approval.5
Internal comments stay hidden from clients
External reviewers don't see internal comments. Check comment visibility, and the Pro plan requirement for attachments, before a client review.16

Adoption checklist

  • Use stable shot, sequence, build, and revision names.
  • Confirm the uploaded file works in the required viewer, then check V4 support for the exact account and Adobe integration in use.
  • Set link permissions and expiration for the intended audience.
  • Name one person to reconcile contradictory notes.
  • Record which version received final approval.

Sources

Official sources checked .

  1. 1Commenting on mediahelp.frame.io
  2. 2Shares in Frame.iohelp.frame.io
  3. 3Frame.io comparison viewerhelp.frame.io
  4. 4Frame.io V4 and Legacy featureshelp.frame.io
  5. 5Frame.io supported file typeshelp.frame.io
  6. 6Adding attachments to commentshelp.frame.io
  7. 7Frame.io versioninghelp.frame.io
  8. 8Requesting and granting project accesshelp.frame.io
  9. 9Frame.io 3D asset supporthelp.frame.io

Unreal Directive is free and ad-free.

If it saved you time, you can help keep it that way.

Donate