File encryption

Upload any file, set a password, and encrypt it in your browser into a .flyenc ciphertext using AES-256-GCM. The recipient cannot open that file directly — they must come back to this site, upload it and enter the correct password to decrypt and download the original. Add an optional password hint, drag files in, and follow chunked progress on large files. Neither the file nor the password is uploaded; passwords are never stored and cannot be recovered if lost.

Free and no sign-up. File encryption computes and renders entirely in your browser; nothing you enter is uploaded.

More tools in Encryption & security

Frequently asked questions about File encryption

Why can't the encrypted file be opened, and how does the recipient view it?
That is exactly the point. The output is a .flyenc ciphertext container: after the header come AES-256-GCM encrypted bytes, with none of the original PDF, image or document structure left, so neither the operating system nor any application recognises it — double-clicking shows gibberish or a damaged-file warning. Send the .flyenc file, then ask the recipient to open this site's "File encryption" page, switch to "Decrypt file", upload the file and enter the password you shared with them separately. They can then download the original file, with its filename restored. Share the password through a different channel, never in the same message as the file.
Can I recover a forgotten password? What happens if I enter the wrong one?
No. This is AES-256-GCM symmetric encryption: the key is derived solely from the password you typed via PBKDF2-SHA256. We store no password, no key and no file, and there is no back door or password-recovery flow — lose the password and the ciphertext cannot be restored. A wrong password is detected immediately after key derivation using a verifier in the file header, so you get "Incorrect password" without decrypting the whole file; nothing is damaged and you can retry as often as you like. Keep the password in a password manager, or add a hint only the recipient would understand when encrypting.
Are my file and password uploaded? Is the encryption strong enough?
Nothing is uploaded. Encryption and decryption run entirely in your browser with Web Crypto, reading the file in 4 MB chunks; the page makes no upload request at all, and refreshing or closing it releases the file, password and key from memory without writing anything to localStorage. The cipher is AES-256-GCM with an authentication tag — changing a single byte fails verification — and the key comes from PBKDF2-SHA256 with 210,000 iterations, with a fresh random salt and nonce for every encryption. The filename and optional password hint sit in the header as plain text so the recipient can identify the file, so never put the password itself in the hint. Password strength is what really matters: use a long password you do not reuse, since a weak one can still be brute-forced offline.
What file sizes are supported? Can I encrypt a folder or several files at once?
A single file should stay under 500 MB. It is processed in 4 MB chunks with a progress indicator, and the practical ceiling depends on available browser memory — compress very large files first. One file at a time: to send several, pack them into a ZIP (or merge them with another tool on this site) before encrypting. The .flyenc output is slightly larger than the original (the header plus a 16-byte authentication tag per chunk). Decryption verifies the header and every chunk tag, and reports clearly when the format is wrong, the wrong file was chosen or the file was truncated.
Do I need to register or pay to use File encryption?
Almost every tool is free, needs no registration or sign-in and has no usage limit; the few pay-per-use features (such as AI watermark removal, AI background removal, AI image generation, AI upscaling, AI ID photos, AI annotation, and AI flowchart, mind-map and Mermaid generation) state their prices on the page.
Is the data I process with File encryption uploaded to a server?
No. Calculation and rendering run locally in the browser and your input is never sent to a server; only the IP address page asks our backend for your outbound address when it opens, and that request carries none of your input. Features that need the backend (such as AI watermark removal, AI background removal, AI image generation, AI upscaling, AI ID photos, AI annotation, AI flowchart and mind-map generation and "Financial statements – Small Business Accounting Standards") state their upload scope on their own pages.

About Local Toolbox

Local Toolbox groups the small tools you reach for every day by what you are doing: formatters and converters, date maths, documents and résumés, codes and ID cards, images, encryption, diagramming, and annotation and accounting. Open a page and start working — no sign-up, and almost every tool has no usage limit.

Most features compute inside your browser, so your input never leaves your device; the pages are plain static assets, load fast and keep working offline. The IP page asks our backend for your outbound address when it opens and sends none of your input. AI watermark removal, AI background removal, AI image generation and AI upscaling send content to our backend for inference (watermark removal is ¥1 per run; background removal is ¥1 per run; image generation and upscaling are priced by resolution — 2K ¥2, 4K ¥3); AI annotation sends images to a large model that locates the target and returns coordinates (¥0.5 per image, refunded only when every image in the batch fails); AI flowchart, AI mind-map and AI Mermaid chart generation send your text description to a model that builds the diagram (three separate products, charged ¥0.5, ¥0.5 and ¥0.5 per run respectively); and the accounting helper sends the income, expense, social-insurance and balance figures you fill in to generate a report (¥0.5 for the spoken analysis, ¥1 for the report). These features accept Alipay and WeChat Pay, upload nothing before payment succeeds, and refund automatically if processing fails.

Links