PRIVATE · ON YOUR DEVICE

A browser media bench for files you already have

Insts keeps local file work in a separate bench from its source resolver. Add one small authorized media file, inspect the available operation and let WebAssembly produce the result on this device. Neither the original nor the output is sent to a downloader worker by this page.

An user-selected local file is the starting point for On-device operation on Insts. An inspection bench then presents browser WebAssembly memory and explains no server upload.

↯ No upload⌁ No server queue◌ Cleared when the tab closes

BROWSER MEDIA LAB

Process locally

Checking this device…

Separate Insts workflow records from your device data

Insts processes each public link, selected format, queue stage, delivery status, and a small set of protected reliability signals. Those server-side records are distinct from recent links and interface settings stored in the browser. Prepared outputs are temporary, continuation tokens are opaque, and local-media tools do not upload the file you open for in-browser conversion. This local page is different: the selected file is read with the browser File API and written into temporary WebAssembly memory, with no media-upload endpoint.

Honest limits for Insts

Insts makes Browser processing limits easy to scan. The page starts with slower WebAssembly work, moves to higher memory use, and clearly states device-aware size gates.

Separate from the Insts download queue

Insts presents three practical points for Queue separation. First comes no downloader worker. The inspection bench then covers no proxy or credit use. Its final point is no delay for visitors.

Process locally

Your local file is ready

Separate Insts workflow records from your device data

Honest limits for Insts

Separate from the Insts download queue