SEAL for your browser
Seal anything you see. Right from the page.
Chrome and Edge, with Firefox in review. Streaming E2EE for large files.

Encrypt before you upload.
The browser is where files leave your machine: into upload forms, CDNs and other people’s clouds. The SEAL extension puts encryption in that path: drag files into the popup, right-click any link or image to seal it, or opt a site into upload interception so files chosen in its forms are encrypted before they leave the tab.
Large files stream: encryption happens segment by segment straight to storage, so nothing buffers in memory. One MV3 codebase runs in both Chrome and Firefox, so there are no per-browser forks to trust.
Segment-by-segment encryption, straight to storage.
“Send via SEAL” on any link, image or media file.
History and owner tokens live in extension storage, never in the DOM.
Three ways in.
The popup
Drag and drop with the full access-rule set: TTL, password, single-use, max opens, geo, NDA.
The context menu
Right-click a link, image or media file anywhere and seal it without downloading first.
Upload interception
Opt in per site; files picked in that site’s upload forms get encrypted before submission.
SEAL is in the Chrome Web Store, for Chrome, Edge and other Chromium browsers. Firefox’s listing is in review at Mozilla.
Questions, answered.
- Who is this for?
- Anyone who sends files from a browser and would rather encrypt before uploading: lawyers attaching case files to web portals, doctors on clinic systems, brokers on deal rooms.
- Where do I install it?
- Chrome, Edge and other Chromium browsers: from the Chrome Web Store. Firefox: the listing is in review at Mozilla; until then seal.net works in every browser without an extension.
- Chrome only?
- Chrome, Edge (Chromium) and Firefox 121+. One source tree, both manifests derived from it.
One seal. Every platform.