Platforms and system requirements

Scribe Animator is a local-rendering editor with optional account and cloud services. Basic editing and a full video export place more demand on the current device than reading a normal web page, so platform compatibility depends on both the operating environment and the features you use.

This matrix reflects the frontend@2.0.0 application and native project configuration reviewed on 31 August 2026.

Supported surfaces

Surface	Current baseline	Best use	Important qualification
Desktop web	A current stable Chrome, Edge, Firefox, or Safari release	Full multi-panel editing, precise timing, long-form projects	Exact older-browser minimums are not published; use an updated browser
Mobile web	A current mobile browser that exposes the required storage and media APIs	Touch-oriented Mobile Lite editing and review	File, microphone, download, and encoder support follow the browser and OS
iPhone and iPad app	Native project deployment target: iOS/iPadOS 17.6 or later	Mobile Lite with native file, share, orientation, and video integration	App Store device eligibility and the installed build remain authoritative
Android app	Android API 24 or later, equivalent to Android 7.0+	Mobile Lite with native file and video integration	Codec and memory behavior still varies by device

Scribe does not publish a fixed CPU, RAM, storage, or GPU minimum in the current product metadata. A device that opens the editor can still be unsuitable for a long 1080p/60 fps export, a very detailed vector trace, or a large local voice model.

Browser capability requirements

Capability	Used for	If unavailable or restricted
JavaScript modules and Web Workers	Editor code, vector processing, image preprocessing, and lazy-loaded features	The relevant editor or worker workflow cannot start
Canvas 2D	Canvas rendering, selection, preview, and frame generation	The core visual editor cannot render correctly
IndexedDB and local storage	Projects, checkpoints, preferences, audio/reveal state, and tutorial progress	Local persistence becomes unavailable or best-effort
Blob URLs and file APIs	Local image, audio, SVG, and package intake	Local sources may not load or survive a new session
WebAssembly	Vector/image utilities, some font and media paths, and fallback encoding	The affected processing or export path can fail
MediaRecorder and microphone APIs	Voice recording, screen-capture encoding, and selected media fallbacks	The relevant recording workflow is unavailable; microphone denial does not block screen-only capture
getDisplayMedia	Desktop browser screen, window, or tab capture	Record screen remains unavailable; normal video upload still works
Document Picture-in-Picture	Optional detached screen-recording controller	Scribe keeps the controls inside the editor instead
WebCodecs or an available fallback/native encoder	MP4 frame encoding and audio/video assembly	Video export can be rejected or routed through a slower/different path
Service workers and Cache Storage	Best-effort application asset caching for repeat and offline use	Editing can still work online, but offline reopening is less reliable
File downloads or native share/save	.scribe, SVG, video, WAV, and other local outputs	The render can finish without a usable delivery destination

Enterprise browser policies, privacy extensions, content blockers, private browsing, and restricted embedded browsers can disable these capabilities even on a supported operating system.

Browser-specific video behavior

The public output is MP4/H.264, but implementation differs:

Runtime	Current video path
Chrome or Edge desktop	WebCodecs where available, with the current audio encoding path
Firefox desktop	WebCodecs video with a WebAssembly media path for audio/muxing where available
Safari 17+ on macOS	WebCodecs video with a WebAssembly WAV-to-AAC and muxing path
iOS/iPadOS native app	Native encoder when available, otherwise the supported WebView fallback
Android native app	Native encoder when available; strict hardware encoder limits can affect resolution/profile choices

This table describes routing, not identical performance. Make a short representative export on the destination device before committing to a long final render.

Desktop screen-recording boundary

Screen recording is a Desktop web feature. It requires both navigator.mediaDevices.getDisplayMedia and MediaRecorder, and the dedicated feature flag must be enabled. The browser's native chooser remains responsible for selecting and authorizing a tab, window, or screen.

Current Chrome/Chromium releases are the validated baseline for the complete capture workflow. When Document Picture-in-Picture is available, Scribe opens the detached recording controller by default; otherwise it uses the in-editor controller. Safari does not currently provide the Document Picture-in-Picture API used by that detached controller, so the separate floating control window is unavailable there. This does not imply that every Safari screen-capture or MediaRecorder combination is validated. Firefox and other browsers likewise use the in-editor fallback when the detached-window API is absent.

Shared or system audio depends on both the browser and selected source. A tab may provide audio while a window or full display provides none. Microphone permission is requested separately, and denial leaves screen-only recording available. Native iOS ReplayKit and Android MediaProjection capture are not part of this Desktop feature.

Permissions by task

Permission	Needed when	Safe response
Files or photos	Importing local media or a .scribe package	Grant access only to the item or folder you intend to use
Screen sharing	Recording a browser tab, window, or screen	Choose only the source you intend to capture; use the browser's Stop Sharing action to end capture
Microphone	Recording voiceover or optional screen-recording narration	Test a short take; screen recording can continue without it
Downloads or storage	Saving video, SVG, WAV, JSON, or .scribe output	Allow the verified Scribe origin/app, then check the saved file
Network	Account, cloud libraries, uploads, billing, first-time remote assets, and model acquisition	Save local work before retrying a failed service
External links	Opening support, legal, payment, or store destinations	Confirm the destination belongs to OHO Tech or the expected provider

Camera permission is not required for the authored Scribe camera system. That camera changes the animated viewport; it does not record the device camera.

Practical device guidance

Use a desktop or a high-memory tablet when the project has:

• many scenes or thousands of objects;
• large raster sources or detailed vector traces;
• several audio tracks;
• local AI voice generation;
• high-resolution or 60 fps video delivery; or
• long preview/export durations.

Use Mobile Lite for focused creation and revisions. Move to Desktop when you need several panels visible at once, dense keyframe editing, prolonged pointer precision, or easier comparison across scenes.

1234

Mobile Lite keeps the same project and timeline domains but presents focused touch surfaces instead of the desktop multi-panel layout.

Screenshot callouts

1. 1
   Project state

   Save and project-file actions remain important before device cleanup or a large import.
2. 2
   Touch canvas

   The viewport adapts to a narrow screen while the underlying scene remains a normal Scribe project.
3. 3
   Expandable timeline

   Expand timing only when needed to preserve canvas space.
4. 4
   Mobile export

   The native or browser encoder still depends on device capability and available storage.

Storage and network checklist

Before a long session:

1. use a normal browser profile rather than private/incognito mode;
2. confirm that site/app storage is not near its OS quota;
3. keep enough free device space for source media and the final export;
4. open the app online once so required application assets can populate their caches;
5. acquire any chosen voice model before going offline;
6. export an editable .scribe backup; and
7. keep remote-only assets out of an offline-critical project unless they are packaged.

Verify your environment in five minutes

1. Create a blank project.
2. Add text and move it on the canvas.
3. Save locally, reload, and confirm recovery.
4. Import one small PNG or SVG.
5. Record or import a short audio clip only if that workflow matters.
6. Export five seconds at 720p/30 fps.
7. Download a .scribe package and reopen a copy.

If one step fails, troubleshoot that capability before building a production project.

Related evidence

• Record your screen and turn steps into editable scenes
• Import and explain video on the canvas
• Supported import and export formats
• Known limitations, offline use, and cloud boundaries
• Create with Mobile Lite
• Troubleshoot Scribe Animator