Scribe Animator Export Performance Benchmark

This benchmark uses the published Marketing Funnel — Awareness to Action Example Project as a real, editable workload. It measures whether Scribe Animator can import and export the complete production correctly at several output profiles. The figures below describe one recorded local run. They are not a speed guarantee for another device or browser.

Workload and release identity

Business Infographic · Marketing

Duration

5:11

Scenes

6

Objects

715

Canvas

1672 × 941, 30 authored fps

Techniques: Camera, Narration, Story Beats, Draw Animation, SVG, Smart Lines, Smart Arrows, Multi Scene, Complex Project.

Watch finished videoOpen editable project

The authored package lasts 311,900 ms (about 5:11), has 6 scenes and 715 objects, and uses a 1672 × 941 canvas at 30 authored frames per second. The runtime audio state contains 78 sources/clips across six tracks. The immutable public package SHA-256 is 2e847b5cdebb52e89f52d9bace205463b3cb9ea252f4b8fd5933c81e775a3796; this value comes from the same public catalog as the editable Marketing Funnel example.

The output profiles below are export settings. A 60 fps output does not change the authored project frame rate.

Recorded export results

All three exports completed and contained audio. The expected and actual frame counts matched, and the output duration matched the project duration.

Profile	Result	Elapsed export time	Expected / actual frames	Output duration	Output size	A/V duration drift
720p30	Passed	380.35 s	9,357 / 9,357	311,900 ms	177,459,522 bytes	83.311 ms
720p60	Passed	723.62 s	18,714 / 18,714	311,900 ms	309,496,353 bytes	83.311 ms
1080p30	Passed	556.04 s	9,357 / 9,357	311,900 ms	204,973,854 bytes	83.311 ms

Package import took about 339.36 ms. Application open and audio readiness took about 2,010.32 ms. A representative JavaScript heap sample was 103,024,268 bytes. A ten-second browser animation-frame sample observed about 32.22 callbacks per second, with a 50.60 ms p95 callback interval.

How to interpret these measurements

• These are a hardware- and load-specific baseline, not a universal export speed or memory promise. Playback responsiveness and encoder throughput depend on the current device, browser, available memory, and competing work.
• The 1080p30 elapsed time includes a documented interval when the benchmark tab was backgrounded and frame production paused. It is not a controlled comparison with the two 720p runs.
• The browser requestAnimationFrame cadence sample is not an exact renderer dropped-frame count. The representative JavaScript heap sample is not total process or GPU memory.
• Correctness and package integrity are hard validation gates. Wall-clock export time is recorded for trend comparison and is not a CI pass/fail threshold.

These distinctions matter when comparing a local run with the table: a slower result does not mean its output is wrong, and a fast result does not excuse missing frames or audio.

How the benchmark is repeated

The runner checks the package's byte length, SHA-256 and expected project structure before opening it through the same safe .scribe import path used by Example Projects. It records import/open timing, scene switching, browser cadence where available, and export results. The completed video is inspected for duration, size, frame count and audio drift. Export errors or package-integrity failures fail the run; timing changes are historical observations.

Scribe Animator's first-party benchmark harness uses the checksum-pinned Marketing Funnel Example Project. It validates package integrity, opens the project through the same safe import path as Example Projects, exports the selected profiles, and verifies frame count, duration, output size, and audio. The three recorded profiles are 720p30, 720p60, and 1080p30. An optional 1080p60 heavy profile exists but was not part of the results shown here.

For related workflows, see choose an export, platform and system requirements, reproducible workflows, and the Example Projects guide.