Are my files actually private?

Yes. KitDevs processes files with browser APIs and WebAssembly. File data is not uploaded to a server.

Does KitDevs use cookies or tracking?

KitDevs does not use tracking cookies, analytics trackers, or advertising pixels.

Do I need to create an account?

No account is required. Open a tool, process a file, and download the result.

What browsers does KitDevs support?

KitDevs works in modern browsers that support WebAssembly and current file APIs, including Chrome, Firefox, Edge, and Safari.

Is there a file size limit?

There is no artificial limit, but available device memory affects very large files.

Frequently Asked Questions

Everything you need to know about KitDevs - how it works, what it supports, and why your files never leave your device.

Privacy & security

Yes, completely. KitDevs processes all files using browser APIs (Canvas, WebAssembly, FileReader). No file data is sent over the network at any point. You can verify this by opening your browser's Network tab in DevTools and observing that no file-related requests are made during processing.

KitDevs does not set tracking cookies, use analytics trackers, or collect personal data. The site may use a minimal functional cookie for preferences in the future, but no third-party advertising or tracking scripts are loaded.

Yes. Because processing happens entirely in your browser, KitDevs is safe for sensitive files - legal contracts, medical documents, personal photos, financial reports. The files never leave your machine, making KitDevs safer than most online tools for confidential content.

General usage

No account is ever required. KitDevs is completely open - open a tool, drop a file, get a result, close the tab. There's nothing to sign up for, no email needed, and no limits tied to an account tier.

KitDevs is free to use with no hidden fees, no premium tiers, and no usage limits. It's funded by non-intrusive advertising on content pages. The tools themselves are entirely ad-free.

KitDevs works in any modern browser that supports WebAssembly and OffscreenCanvas: Chrome 80+, Firefox 79+, Edge 80+, and Safari 15+. For video/audio conversion, Chrome is recommended for the best FFmpeg.wasm performance.

Image tools (compress, resize, convert images) work offline once the page is loaded, since they only use built-in browser APIs. Video/audio conversion requires FFmpeg.wasm to be downloaded on first use (~30MB). PDF tools also work offline after initial load.

Formats & limits

KitDevs currently supports JPG/JPEG, PNG, WebP, and BMP for image tools. GIF support is planned. For compression and resizing, the output can be JPG, PNG, or WebP regardless of the input format.

Input: MP4 (H.264/H.265), MOV (QuickTime), AVI, and MKV. Output audio: MP3, WAV, M4A. FFmpeg.wasm supports a wide range of codecs - if you have a more exotic format, try it and see. Unsupported formats will produce a clear error message.

There's no enforced limit, but practical RAM constraints apply. Images up to 50MB, PDFs up to 100MB, and videos up to 500MB work reliably on a desktop with 8GB+ RAM. The limiting factor is your device's memory - KitDevs imposes no artificial restrictions.

Still have questions?

Check the Glossary for definitions, or open a specific tool guide.

Glossary All guides