Media

Media Safety Standard

Media tools are powerful but browser limits matter. This standard documents the safety promises every MonoTools media utility should make and the constraints it must disclose.

standard

Media tools must be honest about browser limits.

This checklist is a product contract for all media utilities in MonoTools: local-first by default, explicit about memory, and careful not to promise professional transcoding or calibrated measurement when the browser cannot guarantee it.

Local processing

Files are read with browser APIs; no upload is needed for media inspection or export.

Memory pressure

Canvas, decodeAudioData and video seeking can decode full media into tab memory. Prefer bounded dimensions and clear previews.

Cancellation

Long-running tools should expose Stop, reset object URLs and avoid unbounded loops.

Export limits

Browser-native encoders depend on codec support; heavy transcoding is intentionally out of scope until a worker pipeline exists.

Privacy copy

Every media tool must state what is read, what is exported and what never leaves the device.

runtime

Browser-local execution

Inputs stay inside the current tab unless you copy, download or explicitly export.

memory

Session handoff

Magic Paste can pass input to a target tool through sessionStorage, never through the URL.

control

User-owned state

Favorites, recent tools and workflow history are local browser data you can clear from the browser.

smart handoff graph

Suggested next moves

session handoff ready
sponsor

Fixed native slots for developer products. No third-party tracking, no popups, no layout shift.

Sponsor this tool
01

How to use

  1. 01Review the local processing promise.
  2. 02Check memory and cancellation expectations.
  3. 03Use the standard when adding or reviewing media tools.
02

FAQ

Why is this a tool page?
It makes the media lab contract visible to users and contributors instead of hiding it in planning docs.
03

Related tools