Product evidence and compatibility
This section is the public evidence layer for Scribe Animator. It answers questions that are easy to blur in feature tutorials: what is available now, which platforms are supported, which files can cross the product boundary, what still has limits, and how to reproduce a result without relying on a marketing claim.
The information here is derived from the shipping [email protected] product surfaces, package and platform configuration, public documentation fixtures, and current visual product evidence. It was reviewed on 27 July 2026.
Choose the evidence you need
| Question | First-party reference |
|---|---|
| What is the current public product baseline? | Product updates and release status |
| Will Scribe run on my browser, phone, or tablet? | Platforms and system requirements |
| Which files can I import or export? | Supported import and export formats |
| What requires a network or account, and what can fail? | Known limitations, offline use, and cloud boundaries |
| Can I repeat a documented workflow with known inputs? | Reproducible examples and product preview |
| How does a real, complex project export? | Marketing Funnel performance benchmark |
How to read status language
| Label | Meaning in this documentation |
|---|---|
| Active | The feature has a current end-user entry point and documented workflow |
| Beta | The workflow is available, but platform capability, model/runtime availability, or behavior can still vary materially |
| Platform-dependent | The same product action can use different browser, WebView, or native implementations |
| Best-effort offline | Required code and assets must already be available locally, and browser or OS storage can still be evicted |
| Not a public promise | Repository code, an internal surface, or a future direction does not by itself make a supported end-user feature |
The running editor remains the authority for plan limits and conditional controls because entitlement and platform policy can change independently of documentation.
Evidence boundaries
This section deliberately does not publish:
- credentials, account internals, billing implementation details, or production storage keys;
- unreleased, disabled, contributor-only, or development-only capabilities;
- performance claims without a repeatable public test;
- customer outcomes or testimonials that cannot be traced to a real approved source; or
- an unreviewed
.scribepackage or other binary whose contents and checksum are not fixed.
The examples page provides both a readable, asset-free Scribe Template v1 project JSON and a checksum-pinned .scribe package whose import and runtime behavior are covered by product tests.
Report an evidence mismatch
If the running application differs from a table here:
- record the platform and app/browser version;
- capture the visible control or error without exposing private project data;
- test once with the smallest safe project;
- retain the original
.scribebackup; and - use the product support or issue-reporting action.
Do not infer support from a file picker alone. A picker can list an extension even when the current device cannot decode a particular codec or malformed file.