Creators struggle to keep image assets within size limits
Frontend developers lack fine-grained size guardrails for image assets: a broad bundle budget may not enforce stricter limits for formats such as SVG. Bloggers and thumbnail creators also find manual compression tedious, especially when they need to get an image under an upload cap. A separate signal about searching inside large compressed text files describes a different problem and is outside this opportunity.
For frontend developers, technical bloggers, and thumbnail creators. Mentioned from Jan 2019 to Mar 2026 on Bluesky, GitHub and Hacker News.
4 different people described this problem in 4 separate discussions.
- Indie fit
- 6.0/10
- Pain
- 5.0/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Low
What people said
Quoted word for word. Follow a link to read the whole discussion.
The use case here is automation around enforcing filesize requirements for assets to prevent absurd image sizes from being included. While "type": "any" meets this requirement, there are niches of asset types that should have stricter requirements (e.g. svg)
I do thumbnails, it's such a pain all that hard work you do and then reduce it to 2 mbs or what ever that really small limit is
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks