How to Check PDF Forms and Links After Compression

Problem

Compressors may resample images, remove embedded resources, or rewrite the PDF structure. The file can meet a size limit while recipients can no longer enter a name, open a link, download an attachment, or complete the form.

Who should use this

Useful for applications, registration forms, response sheets, manuals, reports with attachments, and approval documents sent to readers who may not know technical workarounds.

Formula and concept

Inventory interactive elements before compression: text fields, checkboxes, menus, signature areas, internal and external links, attachments, bookmarks, and scripts. Without a list, you cannot know what to retest.

Set a size target together with non-negotiable quality and feature requirements. A form usually values fields and links more than a scanned handout; saving a few kilobytes is not worth a broken workflow.

Open the compressed file in a PDF viewer that supports forms instead of relying on a quick browser preview. Adobe’s PDF optimizer guidance describes changes to different resources, so inspect the output in the target viewer (https://helpx.adobe.com/acrobat/using/optimizing-pdfs-acrobat-pro.html).

Test entering, clearing, selecting, required-field prompts, saving, and reopening. Seeing a field outline does not prove it remains interactive or that values survive in every viewer.

Test links through both visible text or buttons and bookmarks or contents navigation. For external links, confirm HTTPS and the full URL; for attachments, test the downloaded filename and contents.

Understand options such as remove interactive content or flatten before selecting them. Flattening can preserve appearance while making fields uneditable; label the deliverable clearly as fillable or archival.

Keep the source PDF, compression settings, and acceptance record. If a recipient reports a broken link or field, rerun a conservative compression from the source instead of patching a damaged copy.

Step by step

1. List fields, links, bookmarks, attachments, and scripts, marking features that must survive.
2. Record the current size, page count, viewer, and reproducible test values.
3. Create a copy with the PDF compressor while retaining the source and settings.
4. In the target viewer, test entering, clearing, saving, reopening, and required prompts.
5. Click text, buttons, contents, and bookmarks, and download each attachment for a content sample.
6. Compare size, searchable text, visual quality, and interaction results before and after compression.
7. Deliver only the version that passes the checklist, labeling it fillable or archival with a version date.

Worked example

A club compresses an 18-page registration form to meet an upload limit. They inventory two text fields, three checkboxes, four external links, and one attachment; after compression the fields are visible but do not save. They switch to a form-preserving setting and test in both a desktop viewer and browser before upload.

Common mistakes

• Comparing file size only without inventorying or testing interactive elements.
• Flattening the file and still delivering it as a fillable form.
• Using only a browser preview and never saving and reopening in a form-capable viewer.
• Not clicking bookmarks, contents, or external links and assuming visible text means a link works.
• Overwriting the only source and losing a baseline for a conservative rerun.
• Compressing exactly to the limit without headroom for platform encoding or attachments.

Related guides

Related workflows