Automation and integrations decision

Save Bulk Gmail Attachments

A competent developer can build and maintain a useful replacement in about a week; the vendor's main durable advantage is an advertised CASA security attestation and existing store presence, not infrastructure or proprietary data, so self-hosting a replacement is realistic.

Visit website
You pay

$4.99/mo

$60/yr

Per seat. Read off the official pricing page.

You’d pay instead

$100one-off36 h to build

$0/mo3 h/mo upkeep

On cash alone, building overtakes the subscription at 2 seats.

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • Select emails in Gmail → extension fetches attachments → upload to Google Drive or generate local ZIP → show progress and resume on reconnect.

What it still won’t have

  • Google CASA Tier 2 security attestation (audit/certification)
  • Chrome Web Store history, reviews and existing user trust
  • Polished UX refinements and edge-case polish for very large batches
  • Enterprise deployment support and in-extension paid subscription plumbing already tested

What remains hard

  • Compliance and regulationGoogle CASA Tier 2 Security Verified
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 2 seats.

Paid seatsseats

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a Chrome extension (Manifest V3) in TypeScript + React for the injected Gmail UI, use Google's OAuth2 flows and Gmail/Drive REST APIs, store session state in IndexedDB, and implement resumable chunked uploads to Drive plus local ZIP creation via jszip. Core features in scope: multi-email selection UI, show per-email attachment counts, one-click 'Save All' to Drive with year/month auto-folder creation, local ZIP download option, resumable uploads/session persistence, and in-extension Pro-feature gating. Out of scope: automated server-side processing, third-party payment processor integration beyond opening a secure hosted payment page, and obtaining Google CASA accreditation. Include error handling, exponential backoff for API calls, unit/integration tests for the pipeline, and CI build + instructions to package and publish to Chrome Web Store.
How we checked3 sources · 2/3 runs agreed · evidence score 81

How the score was reached

  • Build verdict base78
  • 3 cited sources+3
  • Price verified on pricing page+3
  • Hard moats found in the evidence-3
  • Evidence score81

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 3

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ Price read off the page! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat quoted from the page