Straight answers about Fetchora.
What works, what depends on the extractor, what stays in your browser, and what Fetchora refuses to do.
What does Fetchora actually do?
Fetchora accepts a public URL, identifies the platform, asks the best available resolver for media metadata and formats, and offers a signed download path for the files that were actually returned. Local tools can convert or inspect files in your browser.
Why do some platforms need an extraction service?
Platforms such as YouTube and TikTok use authentication, JavaScript challenges, and short-lived stream URLs. yt-dlp handles those cases, but it needs Python and a long-running process. Cloudflare Workers cannot run that environment, so the extraction service is an optional companion.
Does Fetchora store downloads?
No. Fetchora has no media bucket, database, or disk volume. Verified media is streamed from the upstream source through a signed Worker endpoint to your browser. The extraction companion also proxies bytes without keeping them, though its host may have its own logs.
Are private or login-only posts supported?
No. Fetchora does not authenticate as you, accept your cookies, or bypass privacy settings. If a platform serves a login wall, the result reports that limitation and may show only public preview metadata.
Why is a format marked video-only?
Many high-resolution streams separate video and audio. Fetchora marks video-only options so they are never mistaken for a complete file. You can merge compatible local files in the toolkit.
Can I use Fetchora without connecting the extractor?
Yes. Direct media URLs, public page metadata, and the full local toolkit work without it. Social platforms that need the extractor will show metadata-only results or explain that the service is unavailable.
What happens during a browser conversion?
The file is read locally, passed to a WebAssembly FFmpeg build, processed, and returned as a Blob download. The file is not uploaded. The FFmpeg core itself is fetched from jsDelivr when you first use a conversion tool.
Is there a file-size limit?
The Worker does not impose a fixed media-size cap, but very large streams can be stopped by upstream or platform limits. Browser conversions are constrained by available memory; the interface warns above 250 MB and rejects above 1.5 GB.
Does Fetchora support HLS or DASH?
It detects manifests and reports them honestly. A manifest is not a finished video, so Fetchora does not label it as one. Playable renditions require the extraction service or a compatible player.
How do I report a broken extraction or a copyright concern?
Broken sources and rights concerns go to the contact channel configured by the site operator. A public contact address is shown only when one has actually been configured.
Still stuck?
Use the contact page to find the operator's configured support channel. Do not send private media, passwords, or session cookies. Include the public source URL, the error code, and the time of the request if you report a broken resolver.