DEV Community

eugene musebe for Cloudinary

Posted on

5 Projects, 2 Weeks, 1 Goal: Building a More Sustainable Web

Developers talk about sustainability all the time. They talk about it at conferences, in Twitter threads, and in GitHub issue comments. What they do less often is build something about it.

That's what we asked our Cloudinary Creators community to do.

April is widely celebrated as Earth Month, so it felt like the right moment to point that energy at something developers actually have control over: the weight of the web. Digital weight is a real problem, and optimization is still too often treated as an afterthought. We launched the Mini-Hack: Build a Mindful Digital Future, a two-week challenge centered on one idea: the web is heavier than it needs to be, and smarter media delivery is part of the fix.

We wanted to see how developers would use Cloudinary to make digital experiences faster, lighter, and more sustainable across real contexts. No grand prize. No months-long runway. Just two weeks, a focused build, and a Cloudinary swag pack for every valid submission.

The response was better than we expected. In just two weeks, creators built five projects around one shared goal: making digital experiences faster, lighter, and more mindful. A wardrobe. A marketing pipeline. A GitHub Action. An exam-week side project. That range mattered, and it proved the point of the Mini-Hack: sustainability becomes more useful when it shows up as working code.

What We Asked For

The brief was deliberately tight. Pick one focused idea. Build it. Show us what you've got.

Submissions could be a working build with a live demo or repo, a short walkthrough video, or a blog post featuring a specific Cloudinary use case. The theme areas were lighter delivery, asset reuse, sustainability, and storytelling around climate awareness. Earth Month, translated into things you can actually ship.

Two weeks. Simple as that.

What They Built

Five projects came in. All of them different. All of them more thoughtful than a standard hackathon entry tends to be.

EcoLens came from someone who was in the middle of exam week and still shipped. The idea started from something painfully relatable: vibe-coded apps full of unoptimized image.png files that make websites slow for no reason. EcoLens lets you paste a website URL or a GitHub repo link, and it scans for media assets, showing you original vs. optimized sizes, bandwidth savings, and CO₂ reduction estimates, all powered by Cloudinary. The really interesting part is the four ways it lets you act on those results: a one-script-tag SDK method, an npm package for local projects, a GitHub PR flow that opens a pull request with optimized changes, and an AI-guided flow that generates prompts for Cursor, Claude, or Copilot. Stack: Next.js, TypeScript, Supabase, Cloudinary AI transformations, and Vercel.

Check it out:

EcoCloset tackled the problem from an entirely different angle: your wardrobe. The insight is straightforward but easy to miss: most fast-fashion waste happens because people forget what they already own. EcoCloset uses Cloudinary AI to strip backgrounds from clothing photos and build a clean digital lookbook of what's already in your closet. The idea being that if you can actually see your wardrobe before you hit checkout, you buy less duplicate stuff. It's a sustainability tool that works by improving your own visibility into what you already have.

Check it out:

Eco Image Optimizer kept things intentionally simple. Upload an image, run Cloudinary's f_auto and q_auto optimizations, and see the difference: original file size versus optimized, bandwidth savings, and estimated CO₂ reduction, side by side. No complex setup, no steep learning curve. Just a clear, practical demonstration that smarter media delivery has a measurable environmental impact, and that it doesn't have to be complicated to matter.

Check it out:

Green-pipe went in a completely different direction and built for the developer tooling layer. It's a CLI tool and GitHub Action that scans any repository for media assets, optimizes them through Cloudinary, and generates a pull request with the results alongside a bandwidth and carbon report. The builder tested it against multiple real repositories, including the Kubernetes repository, and the numbers made a point all on their own. The project doesn't have a UI. It doesn't need one. It lives where developers already are.

Check it out:

PromptForge AI approached the sustainability problem from the marketing workflow side. The premise: most marketing teams store the same asset in a dozen different formats and sizes, generating storage waste and carbon emissions for no real reason. PromptForge generates a complete marketing kit from a single prompt, then uses Cloudinary to dynamically transform one source asset into every required format. One file. Every format you need. None of the duplication you don't.

Check it out:

The Judging Session

On May 15th, we took it to LinkedIn Live.

Our Official Cloudinary Creators pitched their projects in a live 30-minute session, with Sanjay Sarathy, VP of Developer Experience & Self-Service at Cloudinary, sitting in as guest judge. It wasn't a polished product demo event. It was builders talking through real decisions, real tradeoffs, and real results. Jen Looper and other community members tuned in to watch.

We did not rank the projects or select a single winner. Each submission brought a different approach to the same challenge, and each one showed real thought, effort, and practical use of Cloudinary. For this Mini-Hack, recognition was less about choosing a first place and more about celebrating what every creator managed to build in just two weeks.

You can catch the recording here → Watch the judging session

What These Two Weeks Proved

A two-week mini-hack with a sustainability constraint produced a CLI tool that works on the Kubernetes repo, a wardrobe app that reframes consumption, a PR automation tool, a marketing asset optimizer, and an image audit platform with four distinct developer workflows.

That's a lot of ground to cover for a two-week community event with a swag pack as the prize.

The thread connecting all five projects is the same: digital weight is a real problem, optimization is often an afterthought, and Cloudinary is useful enough that people keep finding new contexts to apply it in. A wardrobe. A marketing pipeline. A GitHub Action. An exam-week side project. That range matters. And it's a fitting way to mark Earth Month: not with a pledge, but with working code.

What's Next

We're doing it again in June.

We're not ready to share all the details yet, but if these two weeks are any indication, it's going to be worth your time. Stay tuned, and if you want to make sure you don't miss the announcement, keep an eye on the community and our social channels.

The web is still heavier than it needs to be. There's more to build.

Want to Be a Creator?

Every project you just read about came from someone in our community who decided to build instead of just talk. You can be next.

Here's where to start.

Learn more about the Cloudinary Creators program and what it offers at https://cloudinary.com/developers/community.

Join the conversation, get build feedback, and hear about the next Mini-Hack first in our Discord community at https://discord.com/invite/D8ddQj6KnH.

When you're ready to go deeper, work through the Cloudinary Creators curriculum at https://training.cloudinary.com/pages/c2c.

Two weeks was all it took last time. See what you can build with yours.

Cloudinary ❤️ developers

Top comments (0)