How-to support ticket attach files screenshot zerodha support portal evidence

How to attach files to a Zerodha ticket

From WebNotes, a public knowledge base. Last updated . Reading time ~9 min.

To attach a file to a Zerodha support ticket, tap Choose file in the create-ticket form and add up to six files, each smaller than 5 MB, or, on an existing ticket, open Track tickets and My tickets on the support portal, tap Choose files and then Reply, or reply to the ticket-update email with the file attached. The 5 MB per-file limit applies on every route.

Evidence is what turns a slow ticket into a fast one. A screenshot of the exact error, a contract note showing the trade, or a bank statement showing a debit lets the support team resolve the matter in the first reply instead of writing back to ask for proof. The mechanics differ slightly depending on whether you are creating a fresh ticket or adding to an open one, and the format of the reply, portal versus email, changes which button you press; the constraints, six files and 5 MB each, do not change.

This guide covers attaching while creating a ticket, attaching when replying through the portal, attaching by email reply, the 5 MB limit and what to do at it, and the practical tricks, combining images into one PDF, compressing screenshots, that keep evidence inside the limits.

Conflict-of-interest disclosure. This guide is published by the WebNotes Editorial Team for informational purposes and is written independently. WebNotes operates a Zerodha account-opening referral programme, disclosed on the pages that carry the referral link; this guide does not carry it and earns no referral commission from the procedure described here.

Step-by-step procedure

The numbered box above lists every route. The sections below expand the three contexts in which you attach: at creation, replying on the portal, and replying by email, plus how to stay under the 5 MB ceiling.

1. Attach while creating the ticket

In the create-ticket form on support.zerodha.com, after you have typed the issue into the Describe your issue in detail box, tap Choose file. Select the screenshot or document from your device. Repeat for additional files, up to six in total, each under 5 MB. The files are listed in the form so you can confirm they are present before you tap Create ticket. Attaching at creation is the cleanest path, because the evidence reaches the team with the first description rather than after a round of questions. The full creation flow is in how to create a ticket at Zerodha .

2. Attach a reply through the support portal

For a ticket already raised, go to support.zerodha.com and tap Track tickets, then sign in with your Zerodha credentials. Open My tickets, where every ticket and its status is listed, and select the ticket you want to add to. Tap Choose files to attach the screenshot or document, then tap Reply to send it. The attachment threads onto the existing ticket, so the support team sees it in context with the original query. This is the route to use when you no longer have the ticket email, or when you want to see the full status alongside your reply; tracking a Zerodha ticket covers the My tickets view in detail.

3. Attach a reply by email

Every ticket update Zerodha sends arrives as an email to your registered address. To add a file, open that email and select Reply, then either use Attach files or paste the file directly into the email body. The reply threads back onto the same ticket through the ticket reference in the subject line, so there is no need to re-enter the ticket number. This is the fastest route when you are already in your inbox reading the team’s last reply. Reply to the latest ticket email, not an old one, so the thread stays single.

4. Keep each file under 5 MB

The hard constraint on every route is 5 MB per file. A modern phone photo can exceed that, and a multi-page scan of statements often does. Before attaching, check the file size. To bring an image down, take a cropped screenshot rather than a full-resolution photo, or compress it. To bring a document down, convert the relevant images to a single PDF and remove pages you do not need. If a file genuinely cannot go below 5 MB, do not abandon the evidence; the large-file route uploads it to cloud storage and pastes a shareable link into the ticket instead.

Accepted formats and the six-file ceiling

Zerodha does not publish a fixed list of accepted file types. In practice, image screenshots and PDF documents are the formats support evidence usually takes, and both attach without trouble. When a file is rejected, it is almost always the 5 MB size limit rather than the format.

The six-file count applies to a single create-ticket submission. If you have more than six images, combine them into one or two PDFs so they count as fewer files. A single PDF of, say, three bank-statement pages is also easier for the team to read in order than three loose images, so the consolidation helps twice. For a large set, one cloud link to a folder is cleaner than many separate attachments.

Why clear evidence shortens the ticket

A ticket with no attachment forces the support team to write back asking for the error screen, the order number, or the statement, which adds at least one 48-working-hour cycle. A ticket that arrives with a cropped screenshot of the exact error, the order or transaction reference , and the relevant date can be resolved in the first reply. The same evidence discipline matters more if the ticket later becomes a formal grievance : the screenshots and statements you attached to the original ticket become the proof you carry to the exchange and to SEBI SCORES . Attach evidence early, keep it under 5 MB, and keep the ticket number that ties it together.

See also

External references

References

  1. Zerodha support, How to attach files while responding to a ticket? (as of 20 June 2026): Track tickets, My tickets, Choose files, Reply, and the email-reply route.
  2. Zerodha support, How do I create a ticket at Zerodha? (as of 20 June 2026): Choose file at creation, up to 6 files each under 5 MB.
  3. Zerodha support, How to attach files larger than 5MB on a ticket? (as of 20 June 2026): cloud-link workaround above the 5 MB limit.

Related articles

Frequently asked questions

How do I attach a file to a Zerodha ticket?
When creating the ticket, tap Choose file and add up to 6 files under 5 MB each. For an existing ticket, open Track tickets and My tickets on the portal, tap Choose files and Reply, or reply to the ticket email with the file attached.
What is the file size limit on a Zerodha ticket?
Each file must be smaller than 5 MB, and a single ticket-creation form accepts up to 6 files. A file at or above 5 MB will not attach; upload it to cloud storage and paste a shareable link into the ticket instead.
Can I attach a screenshot when replying to a Zerodha ticket?
Yes. On the support portal, open My tickets, select Choose files, then Reply. By email, reply to the ticket-update message and attach the screenshot or paste it into the body. Either way it threads onto the same ticket.
What file formats does a Zerodha ticket accept?
Zerodha does not publish a fixed format list; common evidence such as image screenshots and PDF documents attaches without issue. If a file is rejected, it is usually the 5 MB size limit rather than the format that blocks it.
How do I attach more than 6 files?
Combine several images into a single PDF so they count as one file, which also keeps you under the six-file ceiling. For a long set of statements, the cleanest route is one cloud link to a folder pasted into the ticket.
My attachment will not upload to the Zerodha ticket. Why?
Almost always the file is at or above 5 MB, or the connection dropped mid-upload. Check the size, compress an image or split a PDF, and retry. For a file that stays large, use the dedicated large-file workaround.
Does attaching evidence speed up the ticket?
Yes. A screenshot of the exact error, an order number, or a bank debit lets the first reply resolve the issue rather than ask for proof. Tickets with clear evidence typically close in fewer back-and-forth replies.

Reviewed and published by

WebNotes Editorial Team

The WebNotes Editorial Team covers Indian capital markets, payments infrastructure and retail investor procedures. Every article is fact-checked against primary sources, principally SEBI circulars and master directions, NPCI specifications and the official support documentation published by the intermediary in question. Drafts go through a second-pair-of-eyes review and a separate compliance read before publication, and revisions are tracked against the SEBI and NPCI rule changes referenced in the methodology section.

Last reviewed
Conflicts of interest
WebNotes is independent. No relationship with any broker, registrar or bank named in this article.