Read the route
See whether the submitted hostname maps to an enabled source family before evaluating media properties or starting a worker job.
The TikTok compatibility view treats catalog recognition, live metadata, and prepared bytes as different checkpoints. It helps identify what the submitted public URL exposes now and which step would be required for the selected output.
Public or authorized media only. No DRM or access-control bypass.
The QR contains a clean downf.io result link, not an expiring media file. It works for video, audio, images, galleries, documents and playlists.
Checking video, audio and quality options
Paste a public TikTok URL. This page explains supported link families and shows only formats returned for the submitted public link.
See whether the submitted hostname maps to an enabled source family before evaluating media properties or starting a worker job.
Compare container, video presence, audio presence, codecs, resolution, and available size evidence instead of choosing from decorative quality labels.
Distinguish input validation, upstream access, extraction, queueing, processing, storage, and signed-delivery problems when troubleshooting a result.
No recent links stored on this device.
Submit the original public URL and confirm that the displayed service family matches the page or account where the media was published.
Review returned media properties and note whether the preferred option is already combined or needs separate tracks to be prepared.
If the job fails, use the reported stage and timestamp to retry responsibly or send a useful issue report without exposing private material.
Popular services stay in a stable order. The full catalog groups every supported link type under one clear service family.
The TikTok compatibility view treats catalog recognition, live metadata, and prepared bytes as different checkpoints. It helps identify what the submitted public URL exposes now and which step would be required for the selected output.
The TikTok compatibility view treats catalog recognition, live metadata, and prepared bytes as different checkpoints. It helps identify what the submitted public URL exposes now and which step would be required for the selected output.
DownF emphasizes file anatomy: a label such as 1080p is incomplete without its container, audio state, codec information, and delivery path. Estimated size is shown only when metadata or a completed transfer provides defensible byte information.
A recognized TikTok hostname does not override private-account rules, deleted posts, login requirements, DRM, regional delivery, live-window timing, or upstream request limits. Any of those conditions can stop metadata or bytes after catalog detection succeeds.
submitted_url → detect host
platform → matching adapter
formats → live result
Domain presentation and URL routing stay independent.
Start with the common questions. If a public source is not recognized, send it to the automated source check below.
Catalog recognition describes URL routing, while the individual post may be unavailable, restricted, changed upstream, or temporarily unreachable from the active network route.
Many sources expose bitrate or approximate metadata before transfer. DownF keeps estimates distinct from actual bytes observed during preparation and delivery.
Provide the public hostname, approximate time, selected format group, and visible failure stage. Do not send passwords, cookies, private links, or confidential files.
downf.io will test the service. If it is not ready, demand is registered without storing the post path in telemetry.