Local File Encryptor

Encrypt a local file and download a format specification and independent offline decryptor.

On-device No sign-up Free to use

Process file controls

  1. 1 Add files
  2. 2 Arrange/Options
  3. 3 Download

Drop your file here

or choose one from your device

One file

    ?

    Encryption needs at least 12 characters. Keep a separate copy; there is no password recovery.

    ?

    Required when encrypting; ignored when decrypting.

    Result

    Showing an example.

    Encrypt and restore a six-byte text file, retaining its final LF newline.

    Decryption restores fixture.txt containing exactly the six bytes 48 65 6c 6c 6f 0a. The encrypted bytes vary between runs because a fresh salt and IV are used.

    Loading the tool. Your result will appear here.

    https://usefreetools.net/local-file-encryptor · 20 November 2026

    Was this helpful?

    How to use Local File Encryptor

    1. Select Encrypt to .uftenc and choose one original file up to 10 MiB. Enter and confirm a password of at least 12 characters.
    2. Run Process file. Download the encrypted .uftenc file, UFTENC01 format description and independent decrypt-uftenc.mjs script. Keep the password in a separate safe place.
    3. Test recovery before relying on the encrypted copy: select Decrypt a .uftenc file, choose that container and enter the same password. Confirm password is ignored when decrypting.
    4. Compare the recovered file with the original. For independent recovery, use the downloaded script with Node.js 22 or newer and a new output path; it refuses to overwrite an existing file.

    Example: Local File Encryptor

    Encrypt and restore a six-byte text file, retaining its final LF newline.

    You add
    Local file: fixture.txt containing exactly Hello followed by one LF newline (six bytes). Operation: Encrypt to .uftenc Password and confirmation: synthetic-long-password Then choose Decrypt a .uftenc file, select fixture.txt.uftenc and enter the same password.
    You get
    Decryption restores fixture.txt containing exactly the six bytes 48 65 6c 6c 6f 0a. The encrypted bytes vary between runs because a fresh salt and IV are used.

    Options

    Local file
    Choose the local file for Local File Encryptor.
    Operation
    Encrypt creates a custom .uftenc container. Decrypt restores a supported UFTENC01 container with its password; encrypted ZIP decryption is unsupported.
    Password
    Encryption needs at least 12 characters. Keep a separate copy; there is no password recovery.
    Confirm password for encryption
    Required when encrypting; ignored when decrypting.

    Supported inputs and limits

    • Plain files up to 10 MiB.
    • Custom UFTENC01 container using AES-256-GCM and PBKDF2-SHA-256 at 600,000 iterations with a random salt and nonce.
    • Encryption needs at least 12 password characters and confirmation.
    • This is not encrypted ZIP and has no password recovery.
    • Keep a safe original until you test recovery.
    More details

    Native key derivation may finish after Cancel; another job waits until it settles.

    The download includes the exact UFTENC01 specification and a Node.js 22+ decrypt script with no added packages.

    Run it in an interactive terminal with a new output path; existing output files are refused.

    Verify recovery before relying on encryption.

    No streaming or additional container format is provided.

    Where your input is processed

    This tool does not upload your inputs. See the limits for anything saved on your device.

    The container is specific to this tool

    UFTENC01 stores the encrypted file content and its name in a custom AES-256-GCM container. ZIP applications cannot open it. Keep the format description and standalone Node.js 22+ script with the encrypted file, and keep the password separately. The script uses Node’s built-in cryptography, needs no added packages and refuses an existing output path. Successfully decrypt a copy and compare its bytes before removing or replacing an original.

    Authentication failures should stop recovery attempts

    A wrong password or altered container causes decryption to fail; a partial plaintext download is not produced. Do not interpret that failure as a diagnosis of which byte changed. Password strength, trusted-device security and keeping backups still matter. This tool has no independent security certification or password-recovery service.

    Questions about Local File Encryptor

    Can a ZIP app open the encrypted file?

    No. Restore the custom .uftenc format through this page or the downloadable offline Node.js decrypt script. ZIP applications do not recognize this container.

    Can a forgotten password be recovered?

    No. Store the password safely and test recovery before relying on the file.

    Does Cancel immediately stop key derivation?

    No. Native browser cryptography can finish in the background; the tool blocks another job until it settles.

    Page updated · Project managed by Tony Hines · Report a problem with Local File Encryptor