Dev.to WebDev 🛠 Dev 👁 0 📖 1 min read

Video to URL: drop an MP4, get a public link. No signup.

You're wrapping up a demo video, a screen recording, a clip an agent just rendered. Then the boring part starts: the tool you want to feed it to doesn't want a file. It wants a URL. Some social publishing tools work thi

You're wrapping up a demo video, a screen recording, a clip an agent just rendered. Then the boring part starts: the tool you want to feed it to doesn't want a file. It wants a URL.

Some social publishing tools work this way. So do a lot of APIs, automation platforms, and agents. They accept a video URL, not an upload dialog. So you end up pushing the file to some random host, waiting for a transcode you didn't ask for, and getting back a watch page instead of a link to the actual video.

I got tired of that last mile, so I built the thing I wanted: Video to URL, a free tool that does exactly one job. Drop an MP4, get a public, seekable link.

A few things it deliberately does NOT do:

  • No signup. The anonymous link works the moment the upload finishes.
  • No transcoding. The file is stored and served as-is, byte for byte. No recompression, no quality loss, no waiting for a "processing" spinner.
  • No watch page. You get a direct CDN URL you can paste into an API call, an HTML <video> tag, or any tool that takes a video URL. Standard players can seek through it, because the CDN answers HTTP range requests.

The limits, up front: MP4 only, up to 25 MB on the anonymous tool, and anonymous links disappear within 24 hours. If you upload something and want to keep it, there's a "Keep this video" button right on the result: it saves that exact MP4 to a free account, no second upload. Bigger files (100 MB on Starter, 250 MB on Pro) and automated uploads go through the video upload API.

That's the whole thing. A file goes in, a link comes out, and the person opening it never has to know PixelVault exists.

If you try it and hit a wall, tell me in the comments - the tool exists because of walls I kept hitting myself.

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.