Convertly
Media processing and delivery in one platform
When I started working with image optimization, I thought the problem was mostly compression: upload an image, make it smaller, and download the result.
But real media workflows quickly became fragmented. One tool handled compression, another converted formats, another stored assets, and a separate CDN handled responsive production delivery. Automation meant connecting even more services.
Sometimes I only needed to convert or compress an image and take the result elsewhere. Other times, I needed a complete delivery pipeline with responsive widths, transformations, modern formats, caching, and stable production URLs.
I kept wondering why those workflows had to exist as completely separate products.
That led me to build Convertly: one platform for processing, organizing, automating, and delivering media.
Convertly currently includes standalone media tools, a Media API, an image CDN, asset management, and a WordPress plugin. The WordPress integration uses site-specific tokens, so an agency can revoke access for one client without rotating its account-wide API key.
I also built an MCP server for agent workflows. You can approve specific folders on your computer and ask an MCP-compatible agent to organize files, convert formats, compress images, preserve originals, and place the results into new folders - all from one prompt.
For example:
“Scan this product-assets folder, organize the files by product, convert the website images to AVIF, preserve the originals, and place the results in an optimized folder.”
https://convertly.sh/mcp-ai-agents
The platform is live, but it is still early. I am now working on the harder part: finding the clearest entry point and getting it in front of the people who experience these problems.
I would genuinely appreciate feedback: which part sounds most useful to you, the Media API, image CDN, WordPress integration, or MCP workflow?
4 Comments
What stood out to me is that you're trying to replace a workflow rather than a single tool.
People rarely wake up wanting an image CDN or a converter—they want to get media from where it is to where it needs to be with as little friction as possible. Products that align with that journey often feel simpler than their feature list suggests.
Thanks, I really appreciate the feedback. That distinction between selling individual features and removing friction from the entire media workflow is helpful. I’ve been thinking about Convertly as a collection of capabilities, but “getting media from where it is to where it needs to be” is much closer to the actual outcome.
I appreciate you taking the time to explain your thinking.
I'd be interested in continuing the conversation by email if you're open to it. What's the best email to reach you on?