Skip to content
Tutorial

Which browsers can merge and save video

Parsing works in any current browser. Merging is the part that depends on the browser's own capabilities, which is why the same link can succeed on one device and stop on another.

  • No account needed
  • Phone and desktop
  • Public links only

SniffVid TeamPublished Last reviewed

Bot protection

Paste a link above to see every available video, audio and cover download.

By using SniffVid you agree to our Terms of Service and Privacy Policy

The short answer

  • A merged save prefers the File System Access API and otherwise writes a temporary file in browser storage.
  • Merging still works without a save dialog; the finished file is handed to the browser's download location instead.
  • Only codecs that fit the MP4 container are merged, and an incompatible one is named in the error.
  • The output name has illegal characters removed and always ends in .mp4.

These points describe the current download workflow. See the page-specific verification note below for what was checked; upstream availability and returned tracks can change.

An unbranded phone beside a glass file folder and a stack of landscape photo prints.
Concept illustration of a file and a photo library. System menus and supported file formats vary.

Step by step

Follow the controls actually offered by the result panel; formats and browser capabilities can vary.

  1. 1

    Check what your browser can do

    Chromium-based browsers (Chrome, Edge, Opera) can write the merged file straight to a folder you choose. Browsers without that API use temporary storage, which works but needs free space for the whole file.

  2. 2

    Read the message rather than the spinner

    A codec error names the codec that will not fit. A message about the browser being unable to stream large files to disk means the write path is missing, not that the media is unreadable.

  3. 3

    Take the file from where it landed

    With a save picker you chose the folder before the merge started. Without one, the finished file goes to the browser's normal download destination, which is also where you look if the save dialog never appeared.

Desktop and phone browsers beside a merged MP4, with a question mark marking device-dependent support.
The app tries a file picker, then temporary browser storage. A desktop browser is a practical fallback; mobile support depends on APIs, quota and memory.

There are two write paths, and the panel uses the better of the two that exists. Knowing which one your browser takes explains both the save dialog and where the finished file lands.

The two ways a page can write a file

The newer path asks you for a location and streams the merged result into it. The fallback writes into temporary browser storage first and then hands the finished file to the download mechanism. The second path is why a browser can merge successfully and still show no dialog.

When the panel says the browser cannot do it

That message appears only when neither path exists. It is characteristic of an older browser or a restricted embedded view — an in-app browser opened from a social app, for instance — rather than a current desktop or mobile browser. The remedy is a normal browser tab, not a setting.

Codecs MP4 can hold

Merging copies the encoded tracks instead of re-encoding them, so a track the MP4 writer cannot hold is refused rather than converted. The writer accepts the common families — AVC, HEVC, VP9 and AV1 for video, AAC among others for audio — and names whatever falls outside that set. Converting it is not offered.

Phones, storage and long merges

A merge needs room for the whole file, and the fallback path may briefly need a second copy when the temporary file is handed to the download. The tab has to stay open for the duration, even though the screen can be off. Names are trimmed and stripped of characters a file system rejects, so the title you see may differ slightly from the file name.

Reference

These tables are shared across the site, so a figure you saw on one page is the figure you see here.

What works, on what device, and why
TaskDesktopPhoneWhy
Download a public linkDepends on source/browserDepends on source/browserRequires readable media from a provider; the parser does not inherit your platform login.
Download a private, paid or DRM-protected videoNoNoThe source never hands the media to an anonymous reader, so there is nothing to copy.
Save one trackDepends on source/browserDepends on source/browserRequires a readable media file and browser saving support; a manifest alone is not a complete file.
Merge two tracks into one MP4Depends on source/browserDepends on source/browserUses a save picker or temporary browser storage; browser support, quota and memory determine availability.
Convert between formatsNoNoNo decoding or re-encoding: single files keep their supplied format, while compatible track pairs can be remuxed into MP4.
Remove a watermarkNoNoThe file is the platform's own copy; nothing is edited or re-encoded on the way through.
A save sheet with a destination chosen, leading to the Files app listing a saved MP4.
Check Files → iCloud Drive → Downloads first, or use Safari’s download list. Your browser settings may use another location.

Background and edge cases

Single-file results skip all of this

When the platform serves one finished file, saving is an ordinary download and none of the write-path requirements apply. The browser limit concerns split tracks only.

Updating the browser is the fix

There is no toggle that adds a missing write path. A current version of a supported browser, opened as a normal tab, is what changes the outcome.

Frequently asked questions

Usually, through temporary browser storage. The visible difference is that no save dialog appears and the file arrives in the download location, and large tracks need room for the temporary copy.

It exposes a save picker, so the destination is chosen before the merge writes. Declining the dialog cancels the save.

Not without transcoding, which this tool does not do. The error names the codec so you can pick a different track or source.

Characters a file system rejects are removed and the name is shortened, so the output stays writable on every platform. The extension remains .mp4.

How this was checked

How this was checked

Reviewed against the current merge path, its fallback for browsers without a save picker, and the codec check before writing. Devices and browser versions vary; this is a code-based review, not a claim of testing every device.

  • The page-specific note states which behavior was reviewed and which live samples, if any, were tested.
  • Track availability depends on the parsing service. Table sizes are illustrative ranges, not measurements of every video.
  • A source may change or restrict access; the result panel is the reference for the current link.

Who maintains it

Written and reviewed by SniffVid Team, the people who build and run SniffVid. Guides answer practical questions and are updated as capabilities change. Product promotions are labeled separately. Read the editorial policy

Published · Last reviewed · Content last reviewed

Sources and further reading

Primary documentation for the claims on this page. Nothing here cites another downloader as an authority on how downloads behave.

Keep reading

Other tutorials, and the tool pages for the sites people download from most.

Tool pages for the biggest platforms

Dedicated pages combine the downloader with platform-specific link instructions and limits. Choose one below.