Gallery Direct Upload Limits and Formats

Summary

Direct uploads accept specific size and format constraints. Violating limits creates predictable errors you can prevent. For operators, this page should be used as a decision surface, not only as a UI form. Always pair page actions with downstream validation in the relevant live workflow.

What this page is for

• Prevent upload failures.
• Prepare compliant media before upload.
• Reduce operator friction.

Before you start

• Check file size before upload.
• Confirm audio extension and MIME type.
• Split large batches ahead of time.

Step-by-step workflow

1. Open upload dialog in /dashboard/gallery.
2. Select files and review size/type quickly.
3. Upload compliant direct files first.
4. Handle non-compliant files with conversion or alternative flow.
5. Verify successful upload count toast.
6. Re-check asset visibility in grid.

Key states and error handling

• Photo direct limit: 10MB.
• Video direct limit: 50MB.
• Audio direct limit: 20MB with .ogg/.mp3 requirement.

Best practices

• Compress media before peak operations.
• Standardize export settings from content team.
• Prefer predictable file naming with campaign prefix.

Troubleshooting

• Error “No file selected”: select at least one file before submit.
• Error about audio format: convert to .ogg/.mp3.
• Error about audio size: reduce below 20MB.
• If issue persists after one clean retry, capture exact toast/banner text, selected bot, and timestamp before escalation.

UI reference (what each control does)

• Search and type filters control retrieval speed in large media libraries.
• Category selection changes query scope and can hide valid assets if misconfigured.
• Direct upload size limits differ by media type and must be respected.
• Audio pipeline only supports .ogg/.mp3 with strict size constraints.
• Telegram upload sessions are used for controlled constrained ingest paths.
• Batch limits exist for Telegram session uploads and require chunking.
• Bulk actions are powerful and must be validated before applying.
• Upload toasts classify most operational upload failures quickly.

Operator checklist (before shipping changes)

• Verify file formats and size before upload.
• Select correct bot for Telegram upload sessions.
• Upload in small controlled batches to reduce retries.
• Apply categories immediately after successful upload.
• Run periodic uncategorized cleanup to keep retrieval fast.
• Revalidate script media mappings after bulk maintenance.

Real-world scenario

A campaign upload fails minutes before launch. The operator splits files into compliant batches, converts invalid audio formats, runs a Telegram upload session for constrained files, and confirms all assets are visible before script activation.

1. Identify the exact scope (bot, period, module) before any change.
2. Apply one targeted correction based on observed UI state and messages.
3. Validate outcome in the live operational flow linked to this page.
4. Document the final state so future incidents can be solved faster.