Initializing secure environment…
Initializing secure environment…
Assemble the document bundle a GST filing or notice response needs, and get it into a shape the portal will accept. Label each annexure with a page range, merge them in filing order, and compress the result under the 5 MB limit the portal enforces — with the measured size shown before you download. Nothing is uploaded, which matters because these documents contain your PAN, your GSTIN and your turnover. Free, no account, no watermark.
Prepare SCN reply and GST appeal documents for the portal free. Label annexures, merge, and compress under the 5MB limit. No upload, no sign-up, no watermark — and your PAN and turnover never leave your device.
Scans at 300 DPI are the problem, not the text. Convert the bundle at greyscale rather than colour, and if a page is still too large, reduce the resolution to 200 DPI — which is fine for a document that will be read on a screen at the department. Legibility on screen matters; 300 DPI is not a requirement for a portal attachment.
Cover page, index, then each annexure in the order cited in your reply, with a footer on every page giving the annexure and page range. It costs five minutes and it is the difference between a bundle that is read and one that is skimmed because nothing could be located.
Keep the unredacted bundle for the filing; produce a redacted copy for anyone outside your business. Redaction destroys the data permanently, so the order matters: export the full bundle, keep it, then redact. Sending a consultant an unredacted bundle with your PAN and turnover is a habit worth breaking.
A missed GST response deadline carries a much larger cost than any file preparation issue, and it is entirely avoidable. The document work — merging, labelling, compressing — is what a tool can do. Knowing the deadline, drafting the reply, and having it reviewed are yours, and they are the parts that need to start early.
5 MB for most attachments, and it applies per file rather than per submission. The tool compresses to fit and tells you the measured result. If a bundle genuinely cannot get under 5 MB without losing legibility — a scanned document at high resolution — the honest answer is to split it, not to compress it into illegibility.
Consistently and in filing order: Annexure A, B, C, with a one-line description. A footer on every page carrying the annexure name and the page range means any page can be cited — 'page 12 of Annexure C' — which is what an officer reading a bundle needs.
Carefully. If a filing requires the figures, removing them makes the submission invalid. If you are sending the bundle to a consultant rather than to the department, redact with Auto Redact PII first — that is the safe and sensible order: redact for circulation, keep the unredacted original for the actual filing.
This one is the reason the whole site works the way it does. These files contain your PAN, your GSTIN, your registration and your turnover figures. Nothing is uploaded — the bundle is assembled in this tab — and there is no account, so there is nothing to breach and nothing to leak.
Yes. Each labelled document contributes its page range, and a cover index is generated from the labels, with a page range on every page footer. A bundle without an index is much harder for an officer to navigate than one with.
The tool does the document work; it does not know your deadline. Prepare the bundle early rather than the night before, and have the substance of the reply reviewed by whoever handles your filings. Compressing and merging is the easy part and the part that gets left to the last hour.
Yes, and you should. Export the labelled bundle before any redaction, keep it with your filing records, and use the redacted version only for circulation. Redaction is not reversible, and the unredacted original is your evidence that what you filed is what you sent.
Yes. Free, no account, no subscription and no watermark. There is no paid tier because there is no server holding your tax documents.
More business tools — all free, no upload.