How-to support ticket large files 5 mb limit google drive cloud link

How to attach files larger than 5 MB to a Zerodha ticket

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

To attach a file larger than 5 MB to a Zerodha support ticket, upload it to Google Drive, open the file’s share settings, change access from Restricted to Anyone with the link, copy the link, and paste it into the ticket. Zerodha caps direct attachments at under 5 MB per file, so a cloud link is the documented workaround for anything bigger. Compressing or splitting the file under 5 MB is the alternative.

The 5 MB ceiling is a hard one. The Choose file button on the ticket form rejects a file at or above 5 MB outright, with no override. A full-resolution phone photo of a document, a multi-page scanned statement, or a screen recording all routinely exceed it. The fix is not to drop the evidence; it is to either shrink the file or host it where the support team can open it and link to it from the ticket. Zerodha’s own large-file help article documents the Google Drive route, including the single step people miss, switching the link from Restricted to Anyone with the link, that decides whether the team can actually open what you sent.

This guide covers the compress-and-split options that keep a file under 5 MB, the Google Drive upload and the exact sharing setting on both desktop and Android, what to write alongside the link, and the privacy discipline that an Anyone-with-the-link file demands.

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 gives both paths: shrink the file, or share a link. The sections below expand each, with the exact Google Drive steps for desktop and Android and the sharing setting that makes the link usable.

1. Confirm the file is over 5 MB and try to shrink it first

Check the file size before anything else. If it is just over 5 MB, shrinking is faster than uploading. Three reliable ways to get under the limit: take a cropped screenshot of the relevant area instead of a full-resolution photo, which alone often halves the size; run the image or PDF through a compressor; or split a long PDF into parts, each under 5 MB, and attach them as separate files within the six-file ceiling . If combining several images is the goal, convert them to a single PDF and then compress that PDF. If shrinking works, attach normally with Choose file and skip the cloud route.

2. Upload the file to Google Drive

If the file must stay large, for example a screen recording, upload it to Google Drive.

On desktop, go to drive.google.com, click New, then File upload, select the file, and click Open. On Android, open the Google Drive app, tap the plus button, tap Upload, and select the file. Wait for the upload to finish before the next step; a sharing setting on a half-uploaded file does not stick.

This is the step that decides whether the support team can open the file. Click or tap the three-dot menu on the uploaded file. On desktop, choose Share. On Android, choose Manage access, then Change. The file defaults to Restricted, meaning only you can open it. Change that setting to Anyone with the link. A Restricted link sent to support returns an access-denied page, and the team cannot request access fast enough to keep the ticket moving, so the file effectively never arrives. Anyone with the link is the setting Zerodha’s article specifies.

Copy the shareable link. Paste it into the create-ticket description or into your reply on the My tickets view. Add a one-line note saying what the file is, for example “Google Drive link to the screen recording of the order rejection on 18 June”. The note tells the team what they are opening and why it matters, so the link is acted on rather than queried.

An Anyone-with-the-link file is reachable by anyone who holds that exact link. It is not listed publicly or indexed, but the link itself is the key, so treat it like one. Three rules keep this safe. Share only the document the ticket needs, not a whole folder of unrelated statements. Redact anything not relevant to the issue, for example masking account numbers you are not disputing. Revoke access once the ticket is resolved by switching the file back to Restricted or deleting it from Drive. These matter most for the documents support tickets usually involve: bank statements, contract notes , and KYC papers, which carry your financial and identity details.

When evidence feeds a formal grievance

If the matter is heading toward a formal investor grievance , keep your own copy of every large file you shared, not just the link. A cloud link can expire or be revoked, but the SEBI SCORES and SMART ODR stages may need the same evidence weeks later, and you will want it on hand rather than re-uploading under time pressure. Keep the ticket number, the files, and the date you shared each one together. The discipline of clean, accessible, well-labelled evidence is what carries a complaint through the escalation ladder without losing time to “please resend the document” requests at each rung.

See also

External references

References

  1. Zerodha support, How to attach files larger than 5MB on a ticket? (as of 20 June 2026): Google Drive upload, Anyone-with-the-link setting, paste the link into the ticket.
  2. Zerodha support, How to attach files while responding to a ticket? (as of 20 June 2026): the 5 MB per-file limit context.
  3. Zerodha support, How do I create a ticket at Zerodha? (as of 20 June 2026): Choose file, up to 6 files each under 5 MB.

Related articles

Frequently asked questions

How do I attach a file larger than 5 MB to a Zerodha ticket?
You cannot attach it directly. Upload the file to Google Drive, open the file’s share settings, change access from Restricted to Anyone with the link, copy the link, and paste it into the ticket description or reply with a note saying what it is.
Why will my large file not attach to the Zerodha ticket?
Zerodha caps each ticket attachment at under 5 MB. A file at or above that size is rejected by the Choose file button. Either compress or split it under 5 MB, or share it through a cloud link instead.
Which cloud service does Zerodha recommend for large files?
Zerodha’s support article documents Google Drive: upload the file, set sharing to Anyone with the link, and paste the link into the ticket. Any cloud link works as long as the support team can open it without an access request.
Do I have to make the file public to share it?
You must set it to Anyone with the link so the support team can open it without requesting access. That is not the same as listing it publicly; only someone holding the exact link can reach it. Revoke access once the ticket is resolved.
Can I compress the file instead of using a cloud link?
Yes, and it is often quicker. A cropped screenshot replaces a full-resolution photo, an image or PDF compressor cuts the size, and a long document can be split into parts under 5 MB each. If that gets you under the limit, attach normally.
Is it safe to share a bank statement through a Google Drive link?
Use an Anyone-with-the-link setting only for the specific document the ticket needs, and revoke access after the matter closes. Share the minimum, redact what is not relevant, and never post the link anywhere other than the ticket itself.
Will the support team accept a cloud link as evidence?
Yes. Zerodha’s own large-file article instructs you to paste a Google Drive link into the ticket, so a link to an accessible file is the sanctioned route for evidence above 5 MB. Add a short note describing the file.

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.