How Mediapapa Builds Trust and Solves Media Library Chaos for WordPress Sites

There was no single moment, more a slow realisation that kept repeating itself across every client site I touched. Year after year, the same thing, a media library full of files nobody understood and nobody dared to touch. Images uploaded ages ago. Duplicates nobody noticed. Files that might be in use somewhere on the site, or might not. Impossible to say without clicking through every page by hand. Every site owner knows that feeling. The files pile up, you have no idea what is safe to remove, so nothing ever gets removed. The library just keeps growing. Most people treat it like a digital attic and quietly close the door. At some point, we stopped accepting that as normal. The problem was everywhere; it hit every WordPress site regardless of size, and nobody had actually solved it. Most tools addressed one small piece. None put it together. Nicolas, my partner and CTO, had already built the technical foundation. I joined to handle product direction, positioning, marketing, and growth. We are both solving a problem we had lived with for years on real client sites. A clear pain point, an existing codebase, a global market. That is a good project to commit to, don't you think? :D

What worked, WordPress.org. We released a free version and installs started arriving from people who had never heard of us. They searched for a media solution and found us. That channel does the work for you if your product actually solves something real. It is the closest thing the WordPress ecosystem has to an app store, and a lot of plugin developers underestimate it. Reviews come in, the install count climbs, trust builds without you pushing for it. What flopped, assuming people would figure it out. We shipped a solid product and waited. Nobody came. The thing is, nobody is out there searching for Mediapapa specifically. They are looking for a fix to a problem they may not have put into words yet. You have to show up where they already are, talk about the problem they recognize, and do it again and again before they have heard your name. Waiting for word of mouth is not a strategy. It is hope dressed up as a plan. Distribution has to be in the room from day one, not something you sort out after launch.

Anxiety of breaking the site. The media library sits at the core of every page, and people know it. One wrong deletion and images vanish across the whole site. That is not an irrational feeling. It has happened to most people who have run WordPress sites long enough, usually at the worst possible moment. What we heard early on was not "your product is missing a feature." It was "I am not sure I trust this yet." That is a different problem to solve entirely, and it required a different kind of answer. So we built the safety side first and made it visible. Before you remove anything, Mediapapa shows you exactly where that file lives across your site. References update on their own when a file changes. Nothing happens without you seeing it first. We are still working on getting that story across clearly enough. Trust is not a box you tick once. You rebuild it at every step, from first install through to the first time someone actually deletes something.

That it is a compression problem. Every major player in this space sells compression. Smaller files, faster site, done. It is easy to measure and easy to pitch, which is probably why it became the default answer. But compression does not tell you which files are actually in use on your site, which are exact duplicates sitting in your library twice, or which ones you can remove without breaking anything. You can push every image through a compressor and still have a library that is completely out of control. It will just be a more neatly packed mess. The real problem is that most site owners have no idea what is in their media library or how it got there. Files come in through the editor, through clients, through imports, through years of handovers. Nobody audits anything. Compression makes those files smaller. It does not make the situation any clearer. We built Mediapapa to answer the questions nobody else bothered asking, what files do I actually have, which are genuinely in use, and what can go? Those questions come before compression even enters the picture.

Growing the WordPress.org install base. We just launched the free version, and the priority now is getting in front of more practitioners, collecting useful feedback, and shipping improvements with educational content alongside them. We are sponsoring WordCamp Europe in June and treating it as our international launch moment - the right room with the right people. After that, WooCommerce support, deeper AI features, and keeping a close eye on the upcoming WordPress Media Library redesign to make sure Mediapapa moves with it rather than against it.

Ten years across WordPress services, freelance work, then several agencies. I ran projects end to end, client relationships, site architecture, content strategy, launches, and the post-launch firefighting that always follows. Before that, online communities going back to the mid-2000s. I have always been more interested in building the space than in whatever the space happened to be built around. No SaaS background. No product management title. But I knew the WordPress ecosystem from the inside, the tooling, the culture, the distribution logic, the community. How people find plugins. How trust gets built. What the WordCamp circuit actually does for a product like this. That kind of knowledge turned out to matter more than any formal product background would have.

Shipping too late. We came from the agency world, where you build something completely, test it thoroughly, and hand it over when it is done. Clients pay for finished work. That thinking does not carry over to a product. We spent too long building before talking to users outside our own circle, and too long polishing before putting anything in front of real people. The lesson, which everyone tells you and which you will not actually believe until you live through it, a working feature in front of real users teaches you more in a week than a month of internal refinement. People use things differently than you expect. They find corners you did not consider. They walk straight past features you were proud of and ask for things you had not imagined. Ship sooner. Ask for feedback earlier. Treat the first version as a question, not an answer. We know this now, and we remind ourselves every sprint.