Answers about media processing, direct URLs, output quality, privacy and troubleshooting. This page describes the current browser-based release and its known limits.
Are files uploaded to Vaultxon?
In the current static release, local file-picker workflows process selected media in the browser and do not send those selected media bytes to a Vaultxon transcoding endpoint. Site pages and assets still load over the network; MP3 export may request encoder code from a CDN, and the direct-link tool contacts the source host.
Can Vaultxon download any video from any social platform?
No. The direct-link tool is intended for direct media-file URLs where the source permits browser access. It does not extract protected streams from social-media pages or bypass DRM, authentication, paywalls or platform restrictions. Use the platform’s permitted export method or a file you have the right to process.
Why can video-to-audio conversion fail?
The browser must be able to decode the source and support the export path. Unsupported codecs, encrypted media, long duration, high resolution or memory limits can interrupt a job. Try a short non-sensitive sample first, use a current browser and keep the source file until you have checked the full result.
Why did the output format change?
Some workflows re-record or re-encode media instead of copying the original stream. Browser APIs may select a supported container such as WebM. Check the actual output in the target application; do not rely on renaming the extension to change the codec.
Why does a direct URL fail when it opens in another tab?
The source may require authentication, use an expiring signature, redirect to a page instead of a file or block cross-origin reads with CORS. Vaultxon cannot override source-host rules. A URL loading in a tab does not mean JavaScript can read its response.
Will compression always make a file smaller?
No. The result depends on the source codec, dimensions, duration, bitrate and chosen settings. Already compressed media may shrink only slightly, while stronger compression can reduce visual or audio quality. Compare the complete output before deleting the source.
Does audio normalisation repair distorted sound?
No. Normalisation changes the level according to the tool’s method; it does not repair clipping or distortion already present in the source, and it does not guarantee a platform-specific loudness target. Listen to the output and compare it with the original.
Are metadata and subtitle styles always preserved?
Not always. Re-encoding may change metadata or timing; image export can drop metadata or transparency; subtitle conversion may lose styling that the destination format cannot represent. Review the output in the software where you intend to use it.
Is a checksum a malware scan?
No. SHA-256 can help determine whether two byte sequences match a trusted reference. It does not scan for malware, prove provenance or establish permission to use a file. Use trusted sources and appropriate security tools for suspicious content.
What should I include in a support request?
Include the tool URL, browser and operating-system version, source format, approximate file size, settings, exact error and the steps that reproduce the problem. Use a small non-sensitive sample if needed. Never send passwords, login codes or confidential signed URLs.
Does Vaultxon keep downloaded files?
The local workflows create outputs in the browser and offer them for download. Your browser and operating system manage downloaded copies. The hosting provider may keep ordinary connection logs, and direct-link requests reach the source host.
What if the output is incomplete?
Keep the original, try a shorter sample, avoid running several large operations at once, and verify the whole output including its end. If the problem continues, send a reproducible report with the non-sensitive technical details listed above.