Practical explanations

What browser-local media processing really means

A practical guide to file privacy, memory use, codec support and safe output checks.

Learn which files remain on your device, what network requests still occur, how browser memory and codec support affect processing, and how to verify outputs.

Try the tool: Media inspector

Inspect file type, dimensions, duration and file size; optionally calculate its hash.

Open tool →

What local processing means here

When you select a file through a browser file picker, the page can read that File object and pass its contents into browser APIs. Canvas, Web Audio, Blob and MediaRecorder can support operations and generate a downloadable result without sending the media bytes to a Vaultxon transcoding server in this static build.

This architecture can reduce the number of places your source media is stored, but it is not a claim that the entire session is offline. The web page, CSS, JavaScript and some optional libraries still load over the network. A direct-link tool also makes a request to the media host you enter, and the host may receive normal request information.

Local does not mean unlimited

Browsers are constrained by memory, CPU, codec support, tab lifecycle and device power. A long 4K video can use much more memory than a short compressed clip. If a tab is suspended or the device sleeps while the workflow records playback, the job may stall or produce an incomplete output.

The browser also controls available encoders. A video may preview successfully but fail during export because the recording codec is unavailable. MP3 export in this build may load a LAME encoder script from a CDN when that output is requested; this downloads code, not the selected media file.

What data may still leave the device?

The local conversion workflow does not upload the selected media to a Vaultxon processing endpoint in this release. The website still receives a normal page request, and the hosting provider may record IP address, user agent, request time and requested path depending on configuration. Optional third-party code can make its own network request. The direct-link tool asks the original media host for the resource and cannot conceal that request from the host.

If advertising, analytics or embedded services are enabled in a later release, the privacy and consent documentation must be updated to describe the providers and data practices that actually apply. Do not promise that a page has no network activity when it loads remote code or requests a URL.

A good workflow for large media

Start with a short representative sample. Close unused tabs and applications, keep the browser active and ensure the device has enough power. Keep the original file. For a critical deliverable, verify the output in a separate player and compare dimensions, duration, audio, subtitle timing and file size.

If a file repeatedly fails, export a standard intermediate format from the application that created it. A browser tool is convenient for common tasks, but dedicated desktop software is better for unusual codecs, very large projects, multitrack media and delivery specifications.

Privacy and shared devices

Avoid processing confidential material on a public or shared device. Downloaded outputs, browser history and operating-system recent-file lists may remain after the page closes. Revoke or replace preview object URLs when finished, close the tab, and remove copies from shared downloads when appropriate.

Local processing is a design choice, not a security certification. Users should still verify the website URL, avoid suspicious files, keep the browser updated and choose only content they have permission to process.

Network activity versus media upload

ActionWhat happensPrivacy implication
Select a local fileThe browser receives a File object and processes its contents.The media bytes are not sent to a Vaultxon transcoding endpoint in this build.
Request MP3 outputThe page may fetch encoder code from a CDN.Code is requested; the local media remains in browser processing.
Use the direct-link toolThe browser requests the URL from its original host.The source host sees a normal request and may log it.
Open a pageThe web host serves HTML, CSS and JavaScript.Standard access logs may be created by hosting infrastructure.

This distinction is useful when communicating privacy. “The file is processed locally” is more precise than “nothing leaves your device,” which would ignore ordinary page requests, external libraries and requests sent to a link’s original host.

Frequently asked questions

Are files uploaded to Vaultxon?

Selected files are processed in the browser in this static build rather than sent to a Vaultxon transcode server. Some libraries and the source URL tool still create network requests.

Can local processing handle any file size?

No. Memory, codec support, browser behavior and device resources limit the workflow.

Does local processing mean completely offline?

No. The page and optional encoder code may need network access; direct URLs also contact their source host.

Why do tools sometimes produce WebM?

Browser MediaRecorder support commonly exposes WebM options. The available container and codecs vary by browser.

Technical references