Zendesk ticket attachments size limits: A complete guide for 2026

Stevia Putri
Written by

Stevia Putri

Reviewed by

Stanley Nicholas

Last edited February 25, 2026

Expert Verified

Banner image for Zendesk ticket attachments size limits: A complete guide for 2026

File sharing is a core part of customer support. Whether it is a screenshot of an error, a PDF invoice, or a video demonstrating a bug, customers need to send files to get help. But every support platform has limits, and Zendesk is no exception.

This comparison helps you quickly identify which Zendesk channels support your specific file sharing requirements and where limits apply.
This comparison helps you quickly identify which Zendesk channels support your specific file sharing requirements and where limits apply.

If you are hitting Zendesk's file attachment limits and wondering what your options are, this guide breaks down exactly what you need to know. We will cover the specific limits across different Zendesk channels, explain why they exist, and walk through practical workarounds.

Understanding Zendesk ticket attachments size limits

Zendesk imposes file size limits to maintain platform performance, control storage costs, and ensure security. These limits vary depending on which channel the customer uses to contact you: help center, tickets, messaging, or email.

The key thing to remember: these limits are fixed. You cannot pay more or upgrade to a higher plan to increase them. Zendesk explicitly states that it is not possible to increase the attachment size limits across all subscription tiers. If you need to send files larger than the limits allow, you will need to use workarounds or third-party solutions.

At eesel AI, we approach file sharing differently. Rather than bolting file sharing onto a ticketing system, our AI teammate integrates with your existing workflows and handles file sharing through the channels you are already using. We will come back to how this works later.

Attachment limits by Zendesk channel

File limits vary significantly depending on which Zendesk channel your customers use. Let us break down each one.

Tickets and web forms

A screenshot of Zendesk's landing page.
A screenshot of Zendesk's landing page.

The ticket channel has the most generous limits, reflecting its role as the primary support channel for most businesses:

User TypeFile Size LimitFile Count LimitNotes
Authenticated users50MB per fileUp to 500 filesLinked attachments
Unauthenticated users50MB per file5 attachmentsHard-coded spam prevention

Authenticated users (those logged into your help center) can attach up to 500 files per ticket, with each file capped at 50MB. This accommodates most business use cases, though it still blocks very large files like uncompressed videos or large datasets.

Unauthenticated users submitting through web forms face a stricter 5-attachment limit. This is a spam prevention measure that Zendesk does not allow admins to change. If anonymous submissions with multiple attachments are important for your workflow, you will need to require login or use a different submission method.

Email channel

For outbound emails sent through Zendesk, the attachment limits are more restrictive than the raw file size limits suggest:

  • Email attachments: 7MB per file, 10MB total for all attachments in a single email
  • Linked attachments: Up to 50MB per file

When email attachment limits are exceeded, Zendesk automatically converts attachments to linked attachments. This means the file is stored externally and a download link appears in the email instead of the actual file.

There is an important distinction between attachment types:

  • Inline attachments: Files dragged and dropped into the body of an email or comment. The image appears wherever you dropped it.
  • Appended attachments: Files that appear at the bottom of a comment and send as part of the comment's email notification.

All files attached via email are scanned for malware before being sent. If a virus is detected, the attachment is not included in the email notification, and the recipient is notified that an attachment was not sent.

Help center and community

For content in your Zendesk help center, the limits are straightforward:

Content TypeFile Size LimitNotes
Article images and attachments20MB per fileApplies to inline images and file attachments
Community posts and comments2MB per imageLower limit for user-generated content
Number of attachmentsNo established limitUse cloud storage for large collections

The 20MB limit for articles is generally sufficient for screenshots, diagrams, and most PDFs. However, if you need to host larger files like video tutorials or high-resolution assets, Zendesk recommends using a cloud storage service and linking to them rather than uploading directly.

For community posts, the 2MB limit is more restrictive. This is primarily for spam prevention and to keep community discussions focused on text rather than media sharing.

Messaging (Web Widget and mobile SDKs)

Messaging has the same 50MB file size limit as tickets, but with additional constraints:

Limit TypeValueNotes
File size50MB per fileSame as tickets
Attachments per messageOne file onlyMultiple messages needed for multiple files
Supported file types50+ typesIncludes images, documents, audio, video, archives
Private attachmentsNot availableDifferent from ticket attachments

The "one attachment per message" rule is important. If a customer needs to send three screenshots, they must send three separate messages. This differs from tickets where multiple files can be attached to a single comment.

What happens when Zendesk ticket attachments size limits are exceeded

When customers or agents try to send files that exceed the limits, here is what happens:

  • For tickets and web forms: Files exceeding 50MB will be rejected and the user will see a warning message. The ticket may still be created, but without the oversized attachment.
  • For email: When outbound email limits are exceeded (7MB per file or 10MB total), attachments automatically convert to linked attachments. The email notification includes a link to download the file instead of the file itself.
  • For GIF files: When you upload GIF files with a large number of frames, the upload might fail with a timeout error. If this occurs, try recreating the GIF file with fewer frames.

Attachments from earlier comments are included in email notifications as linked attachments. If you add multiple attachments to a reply, the attachments are prioritized based on the attachment type and size. Inline attachments take precedence over appended attachments when calculating size limits.

Zendesk storage limits and management

In November 2023, Zendesk announced a significant change: they began enforcing storage limits with overage charges. This affects how you think about file attachments beyond just the per-file size limits.

How storage works in Zendesk

Understanding the distinction between file and data storage is essential for managing your Zendesk account limits and avoiding overage charges.
Understanding the distinction between file and data storage is essential for managing your Zendesk account limits and avoiding overage charges.

Zendesk tracks two types of storage:

Storage TypeWhat CountsExample
File StorageAttachments linked to ticketsPDFs, images, signatures
Data StorageTicket objects, comments, metadataTicket fields, user records, tags

When a customer emails three 5MB attachments, that consumes 15MB of File Storage. A ticket with multiple comments and custom fields might consume about 5KB of Data Storage.

Storage allocation by plan

Your available storage depends on your Zendesk plan and agent count:

PlanData StorageFile StorageFormula
Support Team10 GB + 50 MB/agent10 GB + 2 GB/agentBase + per-agent allocation
Suite Team10 GB + 50 MB/agent10 GB + 2 GB/agentBase + per-agent allocation
Suite Professional10 GB + 100 MB/agent10 GB + 5 GB/agentBase + per-agent allocation
Suite Enterprise10 GB + 200 MB/agent10 GB + 10 GB/agentBase + per-agent allocation

For example, a Suite Professional plan with 10 agents gets:

  • Data Storage: 10 GB + (10 x 100 MB) = 11 GB
  • File Storage: 10 GB + (10 x 5 GB) = 60 GB

Overage charges

If you exceed your allocated storage, Zendesk displays a notice in the Admin Center. You then have two options:

  1. Reduce usage by deleting old tickets or redacting attachments
  2. Purchase additional Storage Units (500 MB Data + 25 GB File) on a per-unit, per-month basis

The storage dashboard in Admin Center shows your current usage and trends over time, though it does not identify which specific tickets or attachments are consuming the most space. To find large attachments, you will need to use API queries or third-party tools.

Workarounds for Zendesk ticket attachments size limits

Since Zendesk's limits are fixed, here are practical approaches for handling larger files:

Cloud storage links

The simplest workaround is hosting files externally and sharing links:

  • Google Drive: Automatically converts files over 25MB to shareable links in Gmail
  • OneDrive: Integrated with Microsoft ecosystems, supports files up to 250GB
  • Dropbox: Direct sharing links with password protection options
  • Box: Popular for business use with enterprise security features

Best practices when using cloud storage:

  • Set appropriate permissions (view-only vs. download)
  • Use expiration dates for sensitive files
  • Include the link in your Zendesk response rather than the attachment field
  • Consider requiring authentication for access to sensitive documents

Third-party integrations

Several apps in the Zendesk Marketplace extend file handling capabilities:

SendSafely

SendSafely offers a Zendesk integration that supports files up to 10GB with end-to-end encryption. Unlike standard Zendesk attachments, files never touch Zendesk's servers. They are encrypted client-side and stored on SendSafely's infrastructure.

Key features:

  • 10GB file size limit (vs. Zendesk's 50MB)
  • End-to-end encryption using OpenPGP with AES-256
  • Identity verification via one-time passcode
  • Files never stored on Zendesk servers

For teams handling sensitive documents (health records, financial data, legal files), this provides both larger capacity and enhanced security.

Box for Zendesk

Box integration allows agents to access and share Box files directly from tickets. While it does not increase attachment size limits, it streamlines the workflow of sharing large files stored in Box.

Attachment Storage Offload

This category of apps moves attachments from Zendesk to external cloud storage (AWS S3, Azure Blob, etc.) while keeping reference links in tickets. This reduces File Storage usage without losing access to the files.

Storage cleanup strategies

If you are concerned about storage overages, consider these approaches:

Delete old tickets

Zendesk's Timed Ticket Deletion feature (in early access) automatically removes tickets older than a specified number of days. You can also use the Bulk Delete Tickets API endpoint, though API rate limits mean large deletions take time.

Redact attachments

The Zendesk API includes a redaction endpoint that removes the file content while preserving a 5KB reference file. This frees File Storage while maintaining ticket history for reporting purposes. However, this requires API scripting or a marketplace app.

Export and delete

For compliance reasons, you may need to retain ticket data without keeping it in Zendesk. Tools like the Exporter app (Enterprise plans) can export ticket data including attachments, which you can then store in a document management system before deleting from Zendesk.

Choosing the right file sharing approach for your support team

Let us summarize the key points and provide a framework for deciding what works for your situation.

Quick reference: Zendesk ticket attachments size limits

ChannelFile SizeFile CountSpecial Notes
Help Center articles20MBNo limit2MB for community posts
Tickets (authenticated)50MB500 filesPer ticket
Tickets (anonymous)50MB5 filesSpam prevention
Messaging50MB1 per message50+ supported file types
Email (outbound)7MB email / 50MB linkedN/AEmail client limits may apply

Decision framework

This flowchart helps you select the most efficient and secure method for handling file attachments based on your team's specific workflow.
This flowchart helps you select the most efficient and secure method for handling file attachments based on your team's specific workflow.

Use native Zendesk attachments if:

  • Most of your files are screenshots or small documents under 50MB
  • Your team handles a low volume of file-related tickets
  • Simplicity is more important than handling edge cases

Use cloud storage links if:

  • You occasionally need to share files larger than 50MB
  • Your team is comfortable managing file permissions externally
  • Cost is a primary concern (most cloud storage has free tiers)

Consider SendSafely if:

  • You handle sensitive files requiring encryption
  • Files over 50MB are common in your support workflow
  • Security and compliance are priorities

Consider eesel AI if:

  • You want an integrated approach that adapts to your workflows
  • File handling is just one of several support friction points you want to address
  • You are looking for a teammate that learns your business rather than a tool you configure

When you invite eesel AI to your team, it connects to your existing tools (including Zendesk, if that is what you use) and learns from your past conversations, help center articles, and documentation. It can then handle customer inquiries across channels without the same attachment constraints.

A screenshot of the eesel AI platform showing the no-code interface for setting up the main AI agent, which uses various subagent tools.
A screenshot of the eesel AI platform showing the no-code interface for setting up the main AI agent, which uses various subagent tools.

For file sharing specifically, eesel AI can:

  • Guide customers to upload large files through appropriate channels based on file type and size
  • Process and analyze attachments within conversations without hard size limits
  • Integrate with cloud storage providers to handle file transfer workflows
  • Maintain context across conversations even when files are hosted externally

The key difference is flexibility. Rather than working within rigid system limits, eesel AI adapts to how your team actually works. You can start with eesel drafting replies for review, then expand to more autonomous handling as it learns your business.

For teams already using Zendesk, eesel AI can work alongside your existing setup, handling conversations that involve complex file sharing while your Zendesk system continues managing standard tickets. You can explore how eesel AI integrates with Zendesk on our Zendesk integration page.

The bottom line is that Zendesk's attachment limits are manageable for most use cases, but they are rigid. If your team frequently bumps against these limits, the time spent on workarounds (uploading to cloud storage, managing permissions, explaining processes to customers) may outweigh the cost of a solution that handles file sharing more gracefully.

Whatever approach you choose, make sure your team documents the process so customers get consistent guidance. Nothing frustrates customers more than being told to "just email the file" only to have it bounce back due to size limits.

If you are curious about how eesel AI could streamline your support workflows including file handling, you can try eesel AI free or book a demo to see it in action.

Frequently Asked Questions

Zendesk has different limits depending on the channel. Tickets allow 50MB per file with up to 500 files for authenticated users, or 5 files for unauthenticated users. Help center articles allow 20MB per file. Messaging allows 50MB per file with one attachment per message. Email has a 7MB limit for actual attachments but 50MB for linked attachments.
No. Zendesk explicitly states that it is not possible to increase attachment size limits. This applies across all plans from Support Team to Suite Enterprise. The only workaround is to use external file sharing services and include links in your Zendesk responses.
Yes. The 50MB limit for tickets and messaging, 20MB for help center articles, and 2MB for community posts apply regardless of your Zendesk plan. While higher-tier plans include more storage allocation, the per-file size limits remain the same across all tiers.
For tickets and messaging, files exceeding 50MB will be rejected and the user will see a warning. For email channels, the behavior depends on the email client. Gmail automatically converts files over 25MB to Google Drive links, while other systems may bounce the email or strip the attachment.
Yes. SendSafely offers a Zendesk integration that supports files up to 10GB with end-to-end encryption. Box also integrates with Zendesk for file sharing. Additionally, Attachment Storage Offload apps can move attachments to external cloud storage to reduce your Zendesk storage usage.
Beyond per-file size limits, Zendesk enforces total storage allocation based on your plan and agent count. File Storage (attachments) is allocated separately from Data Storage (tickets, metadata). If you exceed your allocation, you will need to either delete old data or purchase additional storage units.

Share this post

Stevia undefined

Article by

Stevia Putri

Stevia Putri is a marketing generalist at eesel AI, where she helps turn powerful AI tools into stories that resonate. She’s driven by curiosity, clarity, and the human side of technology.