Attachment cleanup tool for Gmail storage limits
A file-browser view of Gmail attachments that lets users search, filter, and bulk-delete large attachments to free up storage.
The broad concept is not supported by the evidence. A narrower direction is on file: Retrieval, not deletionEvaluated Aug 14, 2026 · thresholds published at /methodology
Turn this into a build spec
One Universal Core, then the exact file layout your platform expects — CLAUDE.md, .cursor/rules, a Lovable knowledge base, a Bolt prompt under its 400-word ceiling. Evidence travels with it.
32 credits · every platform format after it is 5
Reading an open idea needs nothing. Generating a spec from it calls a model and costs real money, so it needs an account and credits — the cost is shown before you spend anything.
Building this?
Tell everyone else. It shows on this page and on the idea cards, and it collects in your dashboard. Ship it and add the link — we fetch it and re-check it weekly.
Sign in to tell others you're building this.
Supporting evidence2
A user explicitly wanted a file-based view of attachments to review, download, and bulk-remove emails with attachments they no longer needed.
A related complaint shows the broader pattern: users archive everything, can't find things later, and resort to deleting en masse — attachment bloat is part of this storage/organization pain.
Falsifying evidence3
Gmail's native search operators (has:attachment, larger_than:) already provide the core filtering capability, and the evidence shows users struggling with general inbox management [S-390] and message density [S-2330] rather than specifically needing visual attachment browsers—suggesting the problem may not justify a dedicated tool.
The evidence is extremely thin—only three signals across five months, with just one [S-12] directly describing attachment cleanup and none showing recurring pain or willingness to pay. This suggests the problem affects too few users or occurs too infrequently to support a standalone business.
Established email clients like Superhuman [P-2235], HEY [P-2234], and Sanebox [P-2236] already operate in this workflow and could add attachment visualization as a feature if it showed real traction, leaving little room for a single-feature tool to capture meaningful market share.
Most likely cause of death
The most likely failure mode is that Gmail's built-in search (has:attachment, larger_than:) already solves 80% of this for free, so the tool only appeals to a thin slice of users who hit storage limits and are too impatient to learn a search operator — not enough to sustain a business. Defensibility would need to come from a genuinely better bulk-review UX (visual grid, one-click multi-delete with undo, attachment-type filters) plus a wedge into a paid tier (e.g. bulk cleanup as a one-time paid action) rather than competing on organization/archiving with well-funded incumbents like HEY and Superhuman who have no verified revenue proof either.
Demand ladder
A complaint is not a customer. Weighted ×1 / ×3 / ×8 / ×15.
Counted from clustered complaint signals. No candidate-relative commercial check was applied, so no revenue is attributed to this idea.
Verified revenue: not established for this idea. No record ties a revenue figure to a product selling what this would sell.
Momentum
Is this problem getting louder or quieter?
Saturation
How many people are already on it. Most sites hide this.
Problem evidence
Who feels this, how often, and why what they use today does not fix it.
- Who feels it
- Individual Gmail users (prosumers, developers, long-tenured personal accounts) who are approaching or have hit their free 15GB storage ceiling and whose consumption is dominated by old attachments. Secondary: people who archive everything, then cannot find anything, and resort to mass deletion.
- How often
- Episodic, not daily. The pain spikes when the storage warning appears or when sending/receiving starts failing — plausibly once every 12–24 months per account. Nothing in this evidence block establishes frequency; the only dated signals are three isolated posts across April–August 2026.
- Why current fixes fail
- Gmail's own path works but is a message-list path, not a file path. To reclaim space today a user types `has:attachment larger_than:10M`, gets a list of *emails* — not files — with no thumbnail, no type filter, no size column, no running total of space reclaimed. They must open messages one at a time to decide what to keep, download keepers individually, then select and delete, and deleting the email deletes the correspondence along with the file. There is no 'download the ones I want, then drop the rest' step, which is precisely the sequence S-12 describes wanting. The failure is therefore a review-and-triage UX gap at one specific moment (the storage-full moment), not a missing capability — which is also why the gap is narrow: the operator-literate user is already served for free (X-162).
At least one user explicitly wants a file-oriented view of Gmail attachments — see all attachments in one place, download keepers, then remove the emails carrying the rest.
Storage accumulation plus failed retrieval pushes users to destructive shortcuts: 'archive everything, search doesn't find anything later, delete everything.'
Density and scanability of mail views is a real irritant for people managing large mailboxes — one user counts 4–6 messages visible versus 10 in a competing client.
The pain is currently addressable for free inside Gmail using has:attachment and size operators, which caps the willingness to pay for a wrapper around the same action.
Willingness to pay is unverified: the evidence base is three records, all complaint- or intent-tier, two from a single source (Hacker News), with no spend- or revenue-tier signal anywhere in the block.
Five named mature email-management products are already in the adjacent space and none has verified revenue recorded here, so this exact pain has no proven monetisation path in this dataset.
No signal in this block shows anyone paying, or offering to pay, for attachment cleanup — no price point, no purchase, no trial-to-paid mention.
Who buys it
The person who feels the pain and the person who signs are rarely the same.
Who buys it is part of membershipThe buyer, the budget it comes out of, and what these people already pay for.Product concept and MVP
Two versions: the one you deliver by hand first, and the one you build.
Product concept and MVP is part of membershipThe concierge version, the buildable version, and the features deliberately left out.Competitors and alternatives
Including the free workaround people use today, which is usually the real competitor.
Competitors and alternatives is part of membershipDirect products, indirect ones, the workarounds, and where the gap actually is.Pricing model
modelledA proposal, not an observation. Benchmarks come from the data; the ladder is ours.
Pricing model is part of membershipA tier ladder with the reasoning behind each price point.Revenue scenarios
modelledArithmetic on the assumptions listed underneath. Change an assumption and the number changes.
Revenue scenarios is part of membershipBase, upside and aggressive cases with every input written out.Market size
modelledReachable customers, not a top-down industry figure.
Market size is part of membershipHow many buyers exist, what they spend, and how many you could realistically reach.Go to market
Named places, not channel categories. These signals came from somewhere.
Go to market is part of membershipWhere the first ten customers come from, then the first hundred.Roadmap
Each version ships something a user can use. No infrastructure-only phases.
Roadmap is part of membershipVersion by version, with what belongs in each.Pivot paths
Where this goes if the first version does not land — and the number that says it did not.
Pivot paths is part of membershipAdjacent directions, and the measurable trigger for taking one.Risks and kill criteria
The thresholds at which the honest move is to stop. Written before you are attached to it.
Risks and kill criteria is part of membershipRanked risks, and the numeric conditions under which to walk away.Validation plan
Seven days that cost nothing but time and can kill the idea before you build.
Validation plan is part of membershipA day-by-day plan and the interview questions that do not lead the witness.Sources and freshness
Every reference opens the original post. This is the part you should check first.
How sure are we, per claim
Where the data is thin, we say so instead of rounding up.
- demand
- Low
- payment
- No data
- market size
- Low
- competitor gap
- Low
9 references from 2 signals · evaluation written Aug 11, 2026.
Related opportunities
Nearest by what the problem actually is, not by category label.
Application tracker that auto-logs from Gmail + job board emails for active job seekers
A lightweight tracker for job seekers that automatically parses recruiter emails and application confirmations into a single timeline, replacing the manual spreadsheet.
Subscription cancellation concierge that auto-cancels via email receipt scanning
A tool for consumers that scans email receipts to find recurring subscriptions and actually files cancellation requests, not just tracks spend.
Privacy-first bank aggregator that writes to a local file, no credential sharing
A desktop tool for people managing multiple bank/card accounts that pulls transactions into one local file or spreadsheet without handing over banking logins.
Eleven more sections behind this one
Who signs the cheque, what the space already charges, the seven-day validation plan, and the thresholds at which you should stop. Three ideas are open in full so you can judge the depth before paying.
16 people have looked at this · 0 turned it into a spec · 0 say they're building it