Skip to content

Security Architecture

Security & Local Verification Guide

Don't take privacy claims on trust alone. Verify in 30 seconds that Vidto processes every byte locally with zero network uploads.

Updated:

3-Step Self-Verification

  1. Step 1: Open any tool & let static UI load

    Visit any tool such as /mov-to-mp4/ or /video-compressor/. If a tool needs FFmpeg.wasm, you may load it once via the workspace, then inspect DevTools -> Network.

  2. Step 2: Disconnect Wi-Fi or toggle DevTools Offline

    Open Chrome/Edge/Firefox DevTools (F12), switch to the Network tab, set throttling to Offline (or turn on Airplane Mode on your device), and clear the network log.

  3. Step 3: Drop a video and export the result

    Select any local video, run the conversion/compression, and save the exported output. Every read, encode, and write completes with 0 KB uploaded and 0 network requests.

How browser sandboxing protects your footage

Every Vidto pipeline runs inside your browser's origin sandbox and dedicated Web Workers. Stream-copy remuxing and WebCodecs encodes read byte slices directly from local disk via Mediabunny BlobSource without loading whole multi-gigabyte videos into heap at once.

When legacy containers (AVI, WMV, FLV) or complex filters run on FFmpeg.wasm, files are mounted via WORKERFS read-only in worker memory—still completely isolated from external networks.

  • No third-party video transcoding APIs or hidden upload workers.
  • Aggregate pageview analytics never inspect, read, or transmit local video bytes or filenames.
  • Strict HTTPS transport with HSTS (Strict-Transport-Security) for static shell delivery.

Frequently Asked Questions

Does Vidto ever upload video headers or thumbnails to inspect codecs?

No. Video Metadata Inspector and the conversion router read only local header bytes in JavaScript and WASM right on your device.

Why does the Network tab show /ffmpeg/* downloads on legacy tools?

Tools for AVI, WMV, FLV, or 2-pass palette GIF fetch the self-hosted FFmpeg.wasm engine parts from vidto.app over GET requests—never uploading your media—and cache them persistently for offline reuse.