Browser Compatibility

FlowPick feature support across different browsers, including API compatibility matrix, fallback strategies, and browser selection recommendations.

Browser support is specific to a workflow. Installing the extension does not mean that every codec, save method or recording mode is available. Use the checks below before starting a long job.

Browser support overview

BrowserExtensionWeb toolsLarge directory-output jobs
Desktop Chrome / EdgeAvailableDepends on the required codecs and APIsRecommended when the directory picker is available
Desktop FirefoxAvailableCompatible tools can run locallyThe directory-writing queue requires Chrome or Edge
Other Chromium browsersCheck the store and browser policyCheck each tool on the deviceConfirm that directory selection is offered
Edge mobileSupported; installation and available features depend on the Edge version on your deviceDepends on the tool's APIs, codecs and device performanceNo desktop directory-writing queue; use desktop Chrome or Edge for long jobs
Other mobile browsersNot currently listed as supported FlowPick browsersTool availability is not guaranteedNo desktop directory-writing workflow
Safari (including iPhone/iPad)Not supportedOutside FlowPick's supported browsersNot supported

Install the current stable browser and extension from the links on the homepage. FlowPick supports Edge mobile, but mobile systems can pause background jobs and have tighter memory and storage limits. Use desktop Chrome or Edge for large files or queues that write to a chosen folder. Safari is not supported. This page does not promise one minimum browser version for every tool.

Check the feature you need

WorkflowCheck before startingIf unavailable
Download queueA directory picker appears and permission is grantedOpen desktop Chrome or Edge
Local conversionThe tool accepts the input codec and offers the output formatTry another supported output or browser
Audio/video transcriptionThe model downloads and the selected processing mode startsTry the smaller model or CPU mode
GPU processingThe tool reports a usable GPU backendUse the offered CPU mode; speed will differ
Screen recordingThe browser offers a source and audio sharingUse an available capture source; audio is not guaranteed
Source previewThe codec plays and the source permits accessDownload and inspect the result independently

Saving and large files

Directory output writes data as it arrives and avoids retaining the entire download in memory. It still needs working buffers and may need temporary storage for merging. Total memory depends on the tracks, concurrency, processing path and browser.

OPFS is browser-private storage, not the final Downloads folder. A completed temporary result still needs to be saved when the tool asks. Browser storage quotas, private browsing, free disk space and tab suspension can interrupt a job. A Blob fallback may need much more memory; do not use it as evidence that an arbitrarily large file will work.

Keep the tab open until saving finishes. If a task specifically requires direct directory output, switch browsers rather than expecting an automatic fallback to provide the same guarantee.

Source access is a separate requirement

A supported browser can still receive 401/403 responses, expired signatures or blocked cross-origin requests. Extension permissions help with supported requests from the original page; they do not bypass DRM, account restrictions or a server refusing access.

Reproduce a problem

Start with the four-second MP4 sample, HLS playlist or DASH manifest. Note the browser version, operating system, selected tool, error and save method. A successful sample checks a small unencrypted workflow only, not all formats or sizes.

See Online Tools and Known Limitations.