Can a browser download a video link without a server?
Yes, but only when the URL points directly to a public, non-DRM audio or video file and the source host permits cross-origin browser access through CORS. Dhrub Free Tools does not extract media from YouTube, TikTok, Instagram, Facebook, Vimeo, X or other social-page URLs; it does not use account cookies, bypass a login or remove DRM. You must own the media or have permission to save it, and your browser—not Dhrub—contacts the source host, so that host can receive your IP address and ordinary request information.
How to use the tool
Choose the lawful route
For a direct file, paste its complete HTTPS media URL. For your own file, choose it from this device.
Confirm permission and review limits
Confirm ownership or permission, then check CORS, file type, track details, duration and the local size boundary.
Save or create a copy
Save the direct response, or trim and export a compatible local file as MP4, WebM or WAV. Check the finished download before deleting anything.
At a glance
- Social-page extraction
- Not provided
- Direct-link protocol
- Public HTTPS only
- Source connection
- Browser connects directly to the source host
- DRM or protected playback
- Not bypassed or removed
- Local conversion input
- Smaller than 75 MB
- Local outputs
- MP4, WebM and WAV
A direct file URL is not the same as a social-video page
A direct media URL returns audio or video bytes, such as an MP4 or WebM response. A social page is HTML plus application code, account rules, adaptive streams and often signed or protected delivery. This tool deliberately refuses known platform pages, HLS playlists, DASH and Smooth Streaming manifests, private-network hosts and responses that identify themselves as web pages.
The browser uses a credential-free CORS request with no account cookies. The source server must opt in to sharing the response with another origin; otherwise the Fetch standard requires the browser to withhold it. Dhrub Free Tools does not route the request through a proxy, because that would move the URL and media onto a server and create cost, privacy and abuse risks.
- Use a link to the actual file, not a watch, share, post or profile page.
- Use each platform’s official download or account-export feature where it is available.
- Expect the source host to see the network request from your browser.
- Do not use the tool to evade access controls, subscriptions, licences or creator settings.
What local media conversion can and cannot change
For a user-selected local file, Mediabunny can inspect the container, duration and tracks, then create an MP4, WebM or WAV copy in the browser. MP4 and WebM prefer copying compatible tracks and may re-encode incompatible ones, but the operation stops instead of silently dropping a selected track. WAV is explicitly a primary-audio-only export and can become much larger than a compressed source.
Media work is memory- and codec-sensitive. This release limits both local inspection and conversion to files below 75 MB and stops outputs approaching 100 MB. Inspection can recognise common MP4, MOV, WebM, MKV, MP3, WAV, Ogg, FLAC, AAC and MPEG-TS containers, but recognition does not mean every codec can be decoded or written by every browser.
Important limitations
- The tool does not scrape social pages, discover hidden stream URLs, use login cookies or provide a universal platform downloader.
- Direct saving works only for public HTTPS media responses that permit CORS. Redirects are refused; paste the final direct-file URL.
- Browser code cannot independently prove where a public host name resolves, so use only source hosts you recognise.
- HLS, DASH, live streams, encrypted media and DRM-protected playback are refused.
- You are responsible for copyright, licence terms, platform terms and permission from the owner or creator.
- Local conversion depends on available memory and browser codec support; some tracks, trims or containers will fail.
Questions people ask
Can I paste a YouTube, TikTok or Instagram page?
No. The tool identifies common platform pages and directs you to the platform’s official download or account-export route. It does not extract the page’s media.
Does Dhrub receive the media URL?
The private workspace does not send the URL to a Dhrub application server. Your browser contacts the source host directly, and that host receives ordinary network information such as your IP address.
Why does a public link fail with CORS?
Publicly viewable does not automatically mean readable by another site’s JavaScript. The source response must explicitly permit cross-origin access under the Fetch standard.
Can it remove DRM or download a paid stream?
No. Encrypted and protected playback is outside this tool, and it does not bypass subscriptions, access controls or digital rights management.
Primary and project sources
- Fetch Standard — WHATWGPrimary browser standard for requests, redirects, credentials and the CORS protocol.
- Encrypted Media Extensions — W3CPrimary web specification for browser interaction with protected and encrypted media systems.
- Mediabunny project — Mediabunny maintainersPrimary documentation for browser-native media reading, writing and conversion.
- Copyright FAQ — World Intellectual Property OrganizationOfficial overview of authorisation, licences and national copyright exceptions.