Images and file attachments
Where you can attach images, videos, and files in Quackback (conversations, tickets, posts, comments, articles), which file types are accepted, and the size limits.
You can add images, videos, and files in most places people write in Quackback. This article lists where attachments work, which file types are accepted, and the size limits.
Where you can attach files
Where | What you can attach | Size limit |
|---|---|---|
Conversations and tickets (Messenger chat, the portal Support page, email, and team replies) | Almost any file: images, video, audio, PDF, Word, Excel, PowerPoint and other office files, CSV, text, code, and archives such as ZIP | 25 MB per file, 100 MB for video, up to 10 files per message |
Feedback posts and comments on the portal | Images (JPEG, PNG, GIF, WebP, AVIF) and video (MP4, WebM, MOV, M4V) | 5 MB per image, 100 MB per video |
Changelog entries and help center articles (team only) | Images (JPEG, PNG, GIF, WebP, AVIF) | 5 MB per image |
Attachments are not tied to a plan. They work the same on every Quackback Cloud plan.
Attach a file in a conversation
In Messenger, on the portal Support page, or in the inbox composer, use the attachment button or drop files onto the message box. You can send up to 10 files in one message. When someone emails your support address, attachments on the email come into the conversation too.
Common office formats such as .docx, .xlsx, and .pptx are accepted, along with PDFs, CSV files, logs, and screenshots.
Note: Executable and script files (for example .exe, .msi, .dll, .bat, .ps1, and .js) are refused when they come from an anonymous visitor or from inbound email. Renaming the file doesn't get around this: Quackback checks the file's contents as well as its name.
Add images and video to a post or comment
When you write a post or comment on the portal, paste or drop an image or video into the editor. It's uploaded and hosted in your workspace. You need to be signed in to upload.
Screenshots are the easiest way to show a bug. A short screen recording is even better for anything that involves several steps.
Self-hosted: storage is required
Self-hosted only. Uploads are stored in S3-compatible object storage. The Docker Compose setup includes bundled storage, so uploads work out of the box. If you run Quackback another way, configure object storage (for example Amazon S3 or Cloudflare R2) with the S3_* environment variables. Without storage, uploads are unavailable. See Environment variables.
If you put a reverse proxy in front of Quackback, allow request bodies large enough for video uploads. See Set up a reverse proxy.
Related articles
Was this helpful?
Your feedback shapes what we write next.