Shopify Chargeback Evidence File Limits: Prepare Readable Uploads

Prepare evidence against the requirements of the actual response channel, then inspect the exported files for readability. A file that fits the size limit can still be useless if its decisive text is blurred. A beautifully formatted document can still fail if it uses an unsupported type or exceeds the permitted total.

For Shopify Payments responses, check the current Shopify instructions and the live case form before exporting. Do not import limits from a different processor merely because its dashboard looks similar. The source checked on 6 September 2026 provides the following requirements. Shopify’s evidence upload instructions

Record the current constraints

Treat these as a dated reference. Recheck if the form displays different requirements or the payment was processed outside Shopify Payments. For example, Stripe publishes its own evidence limits; those are not interchangeable with Shopify’s upload rules. Stripe’s evidence formatting guidance

Write the relevant limits at the top of your preparation checklist. This prevents a teammate from spending time compressing toward the wrong target. Include whether a limit applies per file, per PDF or to the whole submission; those distinctions are easy to overlook.

Budget space by evidential value

Inventory the artifacts before merging them. Give priority to the pages that establish the decisive facts, then include the context needed to interpret them. Removing redundant screenshots is usually better than shrinking every page until it is difficult to read.

Group artifacts by the evidence categories available in the form. If several customer messages belong in one category, combine the relevant conversation into one supported file. Do not create a PDF Portfolio or a document that merely contains links to separate attachments.

Avoid unnecessary cover pages, decorative images and repeated email signatures. These consume space without helping the reviewer. A compact cover note, clear exhibit references and legible source records usually work better than a heavily designed report.

Keep an uncompressed working master. Export a separate submission copy so that later corrections do not require rebuilding degraded images. Preserve the original source files independently from both versions.

A hypothetical compression decision

A hypothetical merchant has a twelve-page evidence packet containing several full-screen screenshots. The exported file is too large for its intended category. One option is aggressive image compression; another is removing irrelevant dashboard areas and duplicate pages.

The merchant first replaces three repeated tracking screenshots with one complete tracking record. It crops empty interface margins while retaining the source, shipment reference and event details. It removes repeated email signatures but keeps the conversation’s sequence. Only then does it apply moderate image compression.

The final check reveals that the carrier’s address is legible, but a serial number in a product photo is not. The merchant restores that image at higher quality and reduces space elsewhere. The objective is not the smallest file. It is an accepted file in which the material facts remain inspectable.

Use this decision order:

1. Remove exact duplicates and irrelevant pages.
2. Replace long interface captures with complete, focused records.
3. Crop unused margins without losing source context.
4. Export using suitable image resolution and embedded text where available.
5. Compress incrementally and inspect the decisive details after each change.

Check PDF behavior, not just appearance

Open the exported PDF in a standard reader. Confirm page order, orientation, fonts and captions. Make sure there are no password prompts, missing images, unsupported embedded attachments or instructions to visit another website.

Where PDF/A compliance is required, use an export or validation workflow that supports it. Merely renaming a file or printing it to a generic PDF does not establish compliance. Keep any validation result with the working record if your process depends on it.

Review scans and screenshots at a normal reading scale. A page can look sharp when zoomed out while small text remains unreadable. Pay particular attention to timestamps, transaction identifiers, shipping addresses and the words immediately around a highlighted statement.

If a document contains annotations, confirm they survive export in the intended form. An arrow that disappears can leave the caption referring to a nonexistent mark. A highlight that covers text can conceal the very fact it was meant to emphasize.

Use a final file manifest

Maintain a short manifest listing each filename, evidence category, page count, file size and key fact. Sum the final exported sizes, not the sizes of earlier drafts. Confirm that each file in the upload form is the version listed in the manifest.

The reviewer should be able to answer: “Which file contains the decisive record, and can I read it?” If the packet passes the numerical limits but fails that test, revise it before submission. Technical acceptance and evidential clarity are separate checks, and both are necessary for a usable response.

Retain the exact submitted files with the case record. This gives the merchant a reliable reference if a later review asks what the issuer actually received, rather than what the team intended to upload.

Keep the dispute reason, amount and response deadline visible in Lower Chargeback while you prepare your response in Shopify or with your provider.

Monitor Your Disputes

Related reading in this collection:

• Link a Chargeback to the Correct Shopify Order and Payment Record
• Chargeback Withdrawal Letters: Check the Bank Document Before Uploading
• Mastercard 4837: Match the Fraud Defense to the Current Rule Requirements