Route
/file/encrypt
Open the workspace, protect the file, and download the result locally.
When the generic file workflow is the right fit
Encrypt supported files in your browser and download a password-protected .vault package without sending the original file through a server-side workflow.
When Cryptvert is better than native protection
The generic file workflow is the best fit when you want one repeatable process across documents, archives, exports, images, audio, and video instead of relying on separate native protection features for each format.
Best for
- Mixed handoffs where the original file type changes from job to job
- Teams that want one consistent encrypt page and one consistent decrypt page
- Fallback workflows when a format-specific route is not necessary
Not for
- Editing native passwords inside formats like PDF or Office files
- Removing DRM or existing vendor-specific protection
- Workflows that require a hosted audit trail or server-side access controls
Common use cases
- Encrypt exports before sharing them over email or chat
- Wrap archives, reports, screenshots, or prototypes into a .vault package
- Use one route for operational handoffs when multiple file families are involved
Mistakes to avoid
- Using the generic route when a format-specific page would give clearer expectations for the uploader
- Sharing the vault file and password in the same message thread
- Assuming the file is converted into a native passworded document format
Quick checklist
- Choose the generic route when you want the broadest file support
- Generate or enter a strong passphrase before processing
- Store the password separately from the vault package
- Download the result and verify the filename before sharing it onward
Need a tighter file match?
Jump into a format-specific encrypt page when you want the uploader and guidance to match the file you are handling.
Before you send
- Confirm that the selected file is the one you want to protect.
- Keep the vault file and the passphrase in separate channels.
- Test one decrypt cycle first for important or time-sensitive handoffs.
Password reminders
- Store the passphrase somewhere secure before you send the vault.
- Avoid reusing passwords from other sensitive workflows.
- If you share the file with someone else, send the password separately.
What to expect after download
- The downloaded result will be a .vault package.
- The original file is wrapped, not converted into a native passworded document format.
- Review the filename after download so you know exactly what you are sending.
Visible FAQ
What does the generic encrypt route actually do?
Cryptvert encrypts the original file in your browser and wraps it into a .vault package. It does not convert the file into another document format.
Does the generic file route work for many different file families?
Yes. The /file routes are the broad entry points for supported documents, exports, archives, images, audio, video, and other common browser-handled files.
Is the generic route the right fallback when I do not need a format page?
Yes. If you do not need a route like /pdf/encrypt or /csv/encrypt, the generic file route is the right default because it avoids unnecessary format-specific restrictions.
What does the decrypt route restore?
Cryptvert decrypts the .vault package locally and restores the original file name and contents where available, regardless of whether the original file was a document, archive, image, or media asset.