From a public link to a local file

Copy one public link you have permission to download, choose MP4 or MP3, and save the file when the task is ready. No platform account is requested; content requiring login or access bypass is outside scope.

Before you start: rights and limits

• Own the work or have permission to download it. Your use must follow the original platform's terms and applicable law.
• The limit is 100 MiB per file and 10 minutes of media. Files are kept for 1 hour.
• There is one worker by default. Other tasks may queue; duplicate submissions do not make processing faster.
• Tasks require JavaScript and first-party cookies. Clearing cookies or switching browsers may remove access to the current task.

Follow these steps

1. Copy the item's public link

   Use the original platform's share feature and paste one item into the downloader. Do not enter an account profile, password, verification code or private share link.

2. Choose a format and confirm permission

   Choose MP4 for video and MP3 for audio only. The server must inspect the source to determine whether an MP4 audio track is available or an MP3 can be created.

3. Follow the task status

   “Queued” means processing has not started. “Analyzing,” “downloading” and “converting” identify the current stage. When progress is unknown, no percentage is invented.

4. Save the ready file to your device

   Choose “Save file” for a same-site browser download. On a phone, check your browser's downloads or Files app. A ready file is not necessarily saved on your device yet.

If something goes wrong

The task is queued or checking has paused

A queue is not necessarily a fault. Automatic checking has a time and request limit. “Check status again” resumes checking without creating another task.

The link is unsupported, restricted or over a limit

Check the original link, platform restrictions and file requirements. Switching MP4 / MP3 does not solve login, copyright or DRM restrictions.

The session expires

The page attempts to renew the session and explains the result. It never automatically repeats your submission. If your cookie is lost, an older task may no longer be accessible.

The creation result is unknown

A network interruption can make it impossible to know whether the server received a task. The page stops new submissions to avoid duplicates. Consider whether you still need to submit before refreshing later.

The file expires or will not save

Expired downloads cannot be recovered. Before expiry, check your browser's download prompts and device storage. A new submission still needs to meet the original limits.

A known rejection is different from an unknown result

service_not_ready means downloads are not open, queue_full means the task queue is full, and contact_full means the feedback queue is full. These three 503 responses confirm that a record was not created by this request. The page preserves the specific reason and lets you retry manually later, never automatically. The home page shows the service switch before submission. An unknown 500, network failure, timeout or unparseable write response still requires duplicate protection.

How do I stop a task?

Choose “Cancel task”. “Cancellation requested — waiting for processing to stop” means the server received the request but executors may still be running. Bounded status checks continue without repeating cancellation. Only the terminal state after the server confirms stopping is shown as cancelled; a click does not prove file cleanup. Resume status checks manually if they pause. Closing or leaving the page stops browser checks but does not mean the server task was cancelled.

Still stuck? Use the feedback form with the platform, chosen format, error text and approximate time. Never send platform login credentials.