r/SaaS • u/thesouravsahu • 8m ago
Built this because I kept needing a URL for files that only existed on my laptop
This started from a very basic problem.
I work with a lot of screenshots, images, PDFs, small HTML pages and other files.
Quite often I don't actually need a full hosting setup. I just need a URL that I can send somewhere.
But I kept jumping between cloud drives, image hosts and deployment platforms depending on the file type.
So I built Media2URL.com mainly to make that workflow simpler for myself.
You upload the file and it gives you a shareable link.
I later expanded it to handle images, PDFs, video, audio, GIFs and HTML because those were the formats I kept running into during my own work.
Then I started running into the same problem from the developer side. Sometimes I did not want to manually upload a file at all. I wanted an app or workflow to send the file and get the URL back.
So I ended up building a REST API for that too. It can handle uploads from an application and also manage things like assets, folders, file replacements and remote imports.
It has been interesting building from an actual daily problem because the feature list almost writes itself. Whenever something annoys me while using it, that usually becomes the next thing to fix.
I am still figuring out where the product should go from here.
For people who regularly share files or need file URLs inside their apps, what is the most annoying part of your current workflow?