Skip to main content
Version: Current

Choose and verify an export

Export is the final rendering or transfer step. Choose the output from what the recipient needs: an MP4 video to watch or a .scribe package that another Scribe Animator session can reopen and edit.

Before you export​

  1. Save the editable project or export a .scribe backup.
  2. Play the complete project from the beginning.
  3. Check every scene transition, object entrance, draw step, camera move, and audio cue.
  4. Confirm that the canvas aspect ratio matches the destination.
  5. Close unrelated dialogs and pause other CPU-heavy browser tabs or apps.
  6. Make a short, lower-resolution test before a long final render.

Export runs locally on the current device. Keep Scribe Animator open and in the foreground until the export finishes. Closing or reloading the page stops the render.

Pick the correct output​

OutputUse it whenWhat it preservesImportant limitation
Video (MP4/H.264)The recipient only needs to watch or publish the animationRendered scenes, motion, camera, draw animation, and mixed audioIt is no longer editable as Scribe objects
Scribe package (.scribe)You need an editable backup or transferProject data plus package assets supported by the package exporterReopen it in a compatible Scribe Animator version
TemplateYou want reusable scene/block/project structureTemplate-compatible project structure and referenced assetsIt is an authoring resource, not a finished video

Do not use a video as the only backup. Do not use a .scribe package as a public playback file.

Understand the video export dialog​

Open the top-right Export action after previewing the project.

Scribe Animator desktop video export dialog with numbered resolution, frame-rate, quality, format, estimate, device warning, and export controls
Video export settings in the desktop editor. The dialog shows the effective plan limit before rendering.
Screenshot callouts
  1. Resolution
    Choose project size, 1080p, 720p, or 480p. The active plan can clamp the final output.
  2. Frame rate
    Choose 24, 30, or 60 frames per second.
  3. Quality
    Select the target bitrate: Low, Medium, or High.
  4. Format
    The current dialog exports MP4 using H.264 for broad playback compatibility.
  5. Estimated bitrate
    A quick indication of compression, not the final file size.
  6. Local-render warning
    Keep this tab open; navigating away interrupts export.
  7. Export
    Starts rendering with the selected effective settings.

1. Resolution​

  • Project size uses the project canvas dimensions when the plan and exporter allow them.
  • 1080p is a common final delivery size for presentations and full-screen web video.
  • 720p is a good test or lightweight delivery size.
  • 480p is useful for fast previews and bandwidth-constrained review.

The free plan is limited to 720p and includes a watermark in the current build. If the project is 1920×1080 but the effective output says 1280×720, the plan limit is being applied correctly.

2. Frame rate​

  • 24 fps gives a film-like cadence and produces fewer frames.
  • 30 fps is the best default for most explainers and product demos.
  • 60 fps can make fast movement smoother, but roughly doubles the frames compared with 30 fps and increases rendering work.

A higher frame rate cannot repair low-resolution assets or poor animation timing.

3. Quality​

SettingTarget bitrate shown by the editorBest use
Low2 MbpsQuick proof or messaging attachment
Medium5 MbpsMost web reviews and drafts
High10 MbpsFinal delivery where text and fine lines must stay crisp

Quality changes compression. Resolution changes pixel dimensions. Check both.

4. Format and estimate​

The current video dialog exposes MP4 (H.264) for compatibility. The bitrate estimate helps compare quality settings, but duration, audio, scene complexity, and encoder behavior affect the final file size.

Export a video step by step​

  1. Select Export Video (MP4) in the top bar if more than one exporter is available.
  2. Select Export.
  3. Choose the resolution and read the effective plan note.
  4. Choose 30 fps unless the destination specifically needs 24 or 60 fps.
  5. Choose Medium for a draft or High for a final.
  6. Confirm MP4 (H.264).
  7. Select Export in the dialog.
  8. Keep the tab open while the progress phase renders and encodes frames.
  9. When the completion action appears, download or save the file.
  10. Play the downloaded file from beginning to end—not only the first scene.

What success looks like​

  • The progress view completes without an encoder error.
  • The downloaded video has the expected dimensions and duration.
  • Every scene is visible inside the frame.
  • Audio starts at the intended time and remains synchronized.
  • Text, thin strokes, and imported images remain readable.
  • The last frame is not cut off.

Practical setting recipes​

DestinationResolutionFrame rateQuality
Fast internal review480p or 720p24 or 30 fpsLow
Typical web or LMS video720p or 1080p30 fpsMedium
Presentation or product demo1080p30 fpsHigh
Fast motion that genuinely needs it1080p when available60 fpsHigh

Platform upload services may recompress the video. Keep the original downloaded export.

Check an Android export on the destination device​

In the Android app, Auto prefers the supported native encoder. A saved explicit WebCodecs, Native, or MediaRecorder choice remains in effect. Auto can use a supported browser fallback when native encoding is unavailable or the device cannot accept the input format; other native errors can still stop the export.

The native encoder prefers a supported hardware Surface path and keeps a bounded queue of frames in order. Audio is submitted in batches with sample-based timing. These are automatic encoder choices; the export dialog does not expose a Surface or queue setting.

This Android change does not describe the iOS encoder or the browser encoder. It also does not establish a speed improvement for every device. A practical verification uses the same project and final settings you intend to deliver:

  1. Include one drawing-hand reveal, one camera move, and a voice or music cue in a short representative project.
  2. Export at 720p, 30 fps, and Medium first.
  3. Open the saved MP4 in the device's video player. Check the first hand pose, scene transitions, audio start, and final frame.
  4. Repeat with the intended final settings, within the plan and device limits.
  5. Retain the working settings and a .scribe backup before a longer render.

The renderer commits the authored hand pose before capturing a frame, so export should use the project-time pose rather than depend on how quickly the preview screen refreshes. If the hand or camera still differs, record the failing time and settings and follow export troubleshooting.

Verify automated preview, export, and cancellation​

An agent can discover ui.project_frame_preview to show a selected scene at an exact scene-local timeMs. Its overlay uses project pixel dimensions with displayMode: "fit" or "actual". Inspect the displayed frame, then close it with Close, Escape, or action: "hide". A metadata response is not proof that the frame was visually reviewed.

For a running automated video export, inspect export.get_status and use export.cancel with the returned operation ID when you need to stop it. Repeated cancellation of a terminal operation preserves its recorded terminal status and completion time. Check the status after requesting cancellation.

Keep three outcomes separate: the command response, the actual downloaded file, and the client's download detector. A detector timeout alone does not establish that no file arrived. Verify the actual MP4 and native .scribe reopen before reporting delivery or editable persistence.

SVG export availability​

SVG export is unavailable in the download menu and public automation/WebMCP API. Use MP4 for rendered output and .scribe for an editable backup. SVG import, vector artwork and drawing remain supported.

Create an editable backup​

Use File → Export .scribe or the equivalent project-file action for an editable transfer. Store the package separately from the rendered video. Before relying on it:

  1. Finish the current save operation.
  2. Export the package.
  3. Check that it has a .scribe extension.
  4. Reopen a copy in a test session when the project is important.
  5. Confirm that locally imported images, audio, and fonts resolve as expected.

Never edit package internals manually unless you are diagnosing a copy and understand the schema.

Limits and safety boundaries​

  • Export is device-intensive; long projects, high frame rates, large images, and complex paths take longer.
  • Web page visibility, browser memory pressure, and encoder support can interrupt a render.
  • Native iOS/Android encoding can differ from web encoding.
  • Plan limits can reduce effective resolution or add a watermark.
  • An export cannot improve the resolution of a blurry source image.
  • SVG export is unavailable; SVG import and drawing remain supported.
  • The exporter does not replace an editable backup.

Troubleshooting​

SymptomSafest recovery
Export stops partwayKeep the app foregrounded, close unrelated heavy apps/tabs, retry once at 720p and 30 fps
Output is blankReturn to the scene, stop playback, check object visibility and camera framing, then make a short test
Audio is absentConfirm the track is not muted, the source is hydrated, and playback works before exporting
Audio driftsTest at 30 fps, check scene/audio duration boundaries, and avoid changing the project during export
Video is softUse a larger allowed resolution and inspect source asset resolution; bitrate alone will not add detail
Thin lines break upTry High quality and inspect the result at 100%; simplify extremely fine geometry if needed
Download never appearsWait for the completion state, allow downloads for the site, and check device storage
1080p becomes 720pRead the plan note; the current free-plan policy intentionally clamps video to 720p
Browser-verified reference

The annotated dialog above was captured from the running Scribe Animator editor with browser-based UI review. Labels and plan warnings reflect the verified [email protected] UI; encoding availability can still vary by browser and device.