ProductsPrivacyLibraryDocsPricingGitHubAdd to ChromeDownload for Mac

// BROWSER EXTENSION

File slicing in the browser

When you attach a file to a supported AI chat site, Omna steps in between your browser and the upload. It captures the file before the site sees it, sends it to the Omna Mac app for slicing, and swaps in a lean, masked copy — all in the background. From your side, you just clicked attach and picked a file.

3 min readSlice attachments automatically

How interception works

  1. Click the attachment button on a supported site (claude.ai, chatgpt.com, gemini.google.com, perplexity.ai, or chat.deepseek.com) and pick your CSV, Excel, PDF, or Word file as usual.
  2. Omna captures the file at the browser level before it's submitted — the site hasn't seen it yet.
  3. The extension hands it to the Mac app over Chrome's Native Messaging — a secure, local-only channel that never touches the network.
  4. The Mac app slices the file using your most recently typed question, keeps only the relevant rows, and masks any PII in them.
  5. The sliced copy is swapped in — the AI site receives the smaller version and processes it as if it were your original.
  6. A result banner appears above the composer showing rows sent, token reduction, estimated savings, and any PII fields masked.

Slice mode vs. Advisory mode

Switch between these in the popup (gear icon → File Handling). The change takes effect immediately.

Slice mode (default)

Omna intercepts the file, keeps only the rows relevant to your question, masks PII, and swaps in the slice. The AI sees the slice; the original never leaves your machine. Best for most users — maximum token and cost reduction.

Advisory mode

Omna doesn't slice. The original passes through unchanged, but Omna runs its local PII scanner and warns you before you send if it finds sensitive content. Use this when you deliberately need to send the full file.

If the Mac app isn't running

Note: File slicing needs the Mac app installed and running. If it's closed, the extension sends the file unchanged and shows "Omna is not running — file sent without slicing." PII masking in chat keeps working either way, because it runs as WebAssembly in Chrome.

The result banner

BannerColourWhat it means
Token Tax killedGreenFile fit the context window; Omna sent a small, relevant slice — real savings
Token Tax crushedGreenFile was too large for the window; Omna's slice fits cleanly under the limit
Token Tax redirectedAmberEven the slice fills the window — same cost, but the right rows are in it
All rows matchedBlueYour question matched every row, so nothing was filtered — shown for transparency

The banner also shows rows sent vs. total, token-reduction percentage, estimated dollar savings, and a chip for any PII fields masked.

Warning: An "All rows matched" banner means the full file was sent — your question was broad enough to match everything. Narrow the question before attaching to get a meaningful reduction.

What's next