# Universal Multi-Media Broadcast Engine (copyMessage)

> Deliver text, photos, videos, voice notes, stickers, and channel forwards to all users with safe rate-limited pacing.

**Category:** Telegram Bot API — Methods (A-Z)  
**URL:** https://docs.botlify.cloud/universal-broadcast  
**Platform:** Botlify Cloud (https://botlify.cloud)  

---

## Universal Multi-Media Broadcast System

   

Mass announcements and notifications are essential for audience engagement. Botlify Cloud standardizes multi-media broadcasting using Telegram's official `copyMessage` API method, enabling administrators to broadcast any rich content type without uploading files multiple times.

   

## Why copyMessage Outperforms sendMessage

   
| Feature | Traditional sendMessage | Botlify copyMessage Engine |
| --- | --- | --- |
| Supported Content | Plain text / HTML only | Text, Photo, Video, Document, Voice, Audio, Sticker, GIF, Channel Forwards |
| Media Upload Overhead | Re-uploads media on every call | Clones message on Telegram's servers (Zero Bandwidth) |
| Formatting Preservation | Requires manual parse_mode tag parsing | Preserves original captions, spoiler tags, and entities automatically |

   

## Production Implementation Pattern

   

The following engine pattern is recommended for all production bots on Botlify Cloud:

      
```php

```

   
> [!TIP]
> **Safe Anti-Flood Pacing (38ms Sleep)**
> Telegram enforces an outbound limit of approximately 30 messages per second per bot. Pausing execution for usleep(38000) (~38 milliseconds) caps delivery at ~26 messages per second, ensuring smooth delivery without triggering HTTP 429 Too Many Requests or account throttling.

> [!TIP]
> **Botlify Cloud Runtime**
> Credentials are auto-injected in .env — always load them with getenv(): BOT_TOKEN, ADMIN_CHAT_ID, BOT_USERNAME. Main database: database.db (SQLite, WAL mode). Runtime errors: error.log. Quick test: send to $ADMIN_CHAT_ID. Full details: Runtime Reference.