THE PROMISE, ITEMISED

WHAT EACH
TOOL TOUCHES.

The privacy policy says that many tools process files locally. This page takes that sentence apart tool by tool: what each tool accepts, where the work happens, which local component it loads, and whether it writes anything into your browser. It was compiled by reading the code in the shipped package, not from a template.

Three answers that hold for all 43

No request endpoint. Across the 43 tool pages and every script they load, there is no fetch, XMLHttpRequest, WebSocket, EventSource or sendBeacon aimed at a server, and no FormData — which is the object an upload would have to be built from.

No outside script. Every tool page loads only same-origin files. A full sweep of the archive found 8,622 resource references across 541 pages resolving to one domain, with zero third-party scripts, iframes or analytics SDKs.

Work happens in the tab. Decoding, encoding and saving all run on your machine. The network is used to deliver the page once, and then not again during processing.

The two places something is written to your browser

Favourites and the recently-used list live in local storage under fv:favs:v1 and fv:recent:v1: the tool's page path, its name, and when you last opened it. No account, no sync, nothing sent anywhere. Clearing site data removes both.

The second one is narrower and was not described until this page existed. Fifteen video tool pages load a small bridge script that can pass a finished video from Video Studio to that tool. When it runs, it stores the video as a Blob in an IndexedDB database called framivoo-video-studio, in a store named handoff. It only runs when the page is opened with ?framivooImport=1, which is what the Studio hand-off links use; a normal visit never opens the database. The record stays in your browser, and deleting it is a matter of clearing site data.

The tools, one row each

Read this as a manifest rather than a summary: 37 of the 43 tools accept a file, six do not, and every one of them works on your machine. “Local component” means a JavaScript file shipped inside the package — no CDN, no remote module. A tool marked “no file input” never opens a picker; the few that also carry “Studio handoff” can still receive a finished video that way, which is the only route by which they ever get a file.

ToolAcceptsLocal component

Image

Image CompressorJPEG, PNG, WebP—
Image ConverterJPEG, PNG, WebP—
Image to PDFJPEG, PNG, WebP—
YouTube Thumbnail PreviewJPEG, PNG, WebP—
YouTube Thumbnail ResizerJPEG, PNG, WebP—
YouTube Banner ResizerJPEG, PNG, WebP—

Video

Video CompressorMP4, WebM, MOV, MKVStudio handoff
Video CropperMP4, WebM, MOV, MKVStudio handoff
Video File Size Calculatorno file inputStudio handoff
Flip VideoMP4, WebM, MOV, MKVStudio handoff
Loop VideoMP4, WebM, MOV, MKVStudio handoff
Video MergerMP4, WebM, MOV, MKVStudio handoff
Video Metadata CheckerMP4, WebM, MOV, MKVStudio handoff
Video ResizerMP4, WebM, MOV, MKVStudio handoff
Rotate VideoMP4, WebM, MOV, MKVStudio handoff
Change Video SpeedMP4, WebM, MOV, MKVStudio handoff
Video SplitterMP4, WebM, MOV, MKVStudio handoff
Video TrimmerMP4, WebM, MOV, MKVStudio handoff
Video Upload CheckerMP4, WebM, MOV, MKV—
Video Bitrate Calculatorno file inputStudio handoff
Extract Audio from VideoMP4, WebM, MOV, MKVStudio handoff
Video Workspaceno file input—

Audio

Audio ConverterMP3, WAV, M4A, AAC, OGG, FLAC, Opus—
Audio CutterMP3, WAV, M4A, AAC, OGG, FLAC, Opus—
Audio MergerMP3, WAV, M4A, AAC, OGG, FLAC, Opus—
Audio Metadata CheckerMP3, WAV, M4A, AAC, OGG, FLAC, Opus—
Audio Volume ChangerMP3, WAV, M4A, AAC, OGG, FLAC, Opus—

PDF

Subtitles

Creator & specs

Aspect Ratio Calculatorno file inputStudio handoff
Drawing Boardno file input—

Where this page stops

This is a description of the code paths in the package, and it is checkable: the same two-minute test in the guide works on any tool here. It is not a statement about the host's own logs, which record a request for each file served.

If a tool ever gains a feature that needs the network — a model download, a remote API — this page and the policy both have to change before that feature ships, and the table above is where the change would show.

Related