Saving video and audio in Telegram with Media Pocket

Media Pocket accepts a link or file in Telegram and returns prepared media through the same interface. This guide follows the user workflow: get access, send something, choose a suitable result, and understand the queue. You need an existing deployment and an invitation from its operator.

1. Get access to an instance

Open the bot provided by the operator and send /start. Redeem an invitation by sending its bare code or using /redeem CODE. Until access is granted, the bot does not admit the user to its working pipeline.

The operator manages single-use codes, invitations with a redemption limit, and expiring codes. Ask the operator about a code that fails: changing the link format cannot repair an expired invitation. Inline mode also requires access and does not replace activation.

2. Send a link or upload a file

For one download, send a supported link as an ordinary message. You can also send several links together. Sources include video platforms, social posts, audio services, and direct HTTP(S) media-file URLs. Support depends on the provider; an arbitrary web page does not necessarily resolve to downloadable video.

The bot also accepts Telegram video, audio, photos, animations, documents, voice messages, and video notes. These enter the same background pipeline. Audio and video may be normalized for Telegram, photos prepared in a suitable format, and ordinary documents preserved as files. The instance’s size limits and access controls apply to both links and uploads.

3. Choose video, audio, or file delivery

Ordinary links start immediately in the source’s natural mode. An audio-first source stays audio. For YouTube, /settings lets you save a preference for video, audio, or asking on every request. Only the last choice opens a format card before downloading.

Use /video URL to request video explicitly. Content format and delivery method are separate choices. Video or audio can play directly in the chat; file delivery preserves the downloaded original where possible. Additional actions arrive separately from a completed result and may offer another format when applicable.

4. Wait for the result or check status

After queueing a job, the bot updates one progress message. Queue position, speed, size, and estimated time appear when available. Long downloads run in the background; resending the same link does not make a worker faster.

The /status command shows your active and recent jobs, along with available cancellation or retry actions. A failure leaves a compact card explaining the reason and next step. Read it first: a network failure, a source restriction, and an oversized file require different responses. After success, the technical status disappears and the finished media remains in the chat.

5. Decide what to do with a collection

A YouTube URL can refer to both an individual video and a playlist. In that case, the bot asks whether you want the current video or the whole collection before queueing anything.

When a single video’s description contains usable timestamps, an option to split its audio into tracks appears. It downloads the audio once, uses the detected boundaries, and sends tracks in groups with titles and metadata. Albums and ordinary media groups are also delivered as collections, followed by separate result actions.

Several links in one message keep each source’s natural mode. If the batch includes YouTube configured to ask for a choice, one choice applies to the batch with a suitable fallback for its other items.

Frequently asked questions

How do I get only the audio from YouTube?

Select audio for YouTube through /settings, then send the link. To decide separately each time, save the ask-every-time preference. This choice applies to YouTube; audio-first sources do not need an artificial video mode.

Will the original quality be preserved?

File delivery preserves the downloaded original where possible. For Telegram playback, the service prefers compatible source streams and remuxing without re-encoding, but incompatible media may require conversion. For heavy direct URLs, the bot can separately offer an original or compact version. This is not a promise to avoid transcoding under every condition.

Why does a link work in my browser but fail in the bot?

Private, deleted, region-restricted, or authentication-gated material may remain unavailable. The bot does not bypass provider access controls. If an instance needs browser cookies, that is a separate operator configuration task; its boundaries are explained in the Media Cookie Broker article. The practical transfer workflow is covered in the server-downloader cookie guide. Never publish passwords or cookie files in an error report.

Is there a shared bot without registration or an invitation?

The project describes a self-hosted, invite-only downloader. You need the address of a particular instance and permission from its operator. This guide does not promise a shared public service or access to someone else’s deployment.