Long-tail task
Use this when your attachment has strict file-size limits but still needs to stay readable.
Break large reports into sections before optimization.
Drop annexes and references that are not required for submission.
Apply balanced or maximum profile based on upload limit.
Prefer split first, then compress.
Use balanced mode, avoid overly aggressive grayscale.
Enable grayscale and remove unnecessary pages before final export.
Run split-by-count and send in two files with clear naming.
Switch from maximum to balanced, then only trim pages instead of extra compression.
Compress sections separately, then merge the smallest successful versions.
Needs to email policy and invoice packet to external client.
Recipient-side confusion usually starts from these two issues.
Checkpoint: File naming follows one visible convention.
Email deliverability improves without aggressive visual loss.
Checkpoint: Attachment stays within mailbox policy.
Cross-device check catches hidden compatibility issues.
Checkpoint: Second device opens and scrolls all pages correctly.
Expected outcome: Recipient can open, review, and approve without resubmission.
Avoid this: Only checking sender-side openability before handoff.
| Signal | Likely cause | Recommended fix |
|---|---|---|
| Email gateway rejects file | Attachment limit or policy blocks are not fully handled. | Apply strict-size workflow and split into two named parts if needed. |
| Recipient says pages are out of order | Merge/reorder sequence changed during final export. | Lock sequence in reorder step and rerun final export. |
| Attachment is accepted but unreadable | Over-compression on charts and small text. | Rollback one compression level and trim non-critical pages. |