Start with a packet, not a pile of attachments
A useful PDF packet has a purpose and an order. Imagine applying for a workshop: the recipient needs a cover sheet, a two-page project description and a one-page reference. Sending four loosely named files leaves them to reconstruct the sequence. Preview can assemble those pages, correct their orientation and add a small explanatory note without requiring a separate PDF subscription.
This workflow concerns ordinary PDFs you own or are permitted to edit. It is not a method for bypassing document restrictions or preserving a digital signature after modification. A signed or locked form may need to remain unchanged. Keep that original separate and ask the recipient whether an additional cover document is acceptable. For a normal packet, duplicate the source files in Finder first and work in a clearly named folder such as Workshop packet working.
Assemble the pages in an intentional order
Open the main PDF in Preview and choose View > Thumbnails. The sidebar is your page-order control; the large page on the right is the place to read the content. Select the thumbnail after which the next file should appear, then choose Edit > Insert > Page from File. Select the additional PDF and inspect where its pages arrived. You can also drag page thumbnails between open PDFs, but confirm the destination insertion position before releasing the pointer.
For the workshop example, insert the project description after the cover, then insert the reference after the description. Drag thumbnails within the sidebar to correct the order. Select a sideways page and use the rotate control until both text and page orientation make sense. A landscape diagram may belong in landscape orientation; forcing every page upright by its paper shape can make the diagram harder to read.
Select an unwanted thumbnail and press Delete only in your working copy. Removing a page also removes its annotations. Before saving, count the expected four pages and read the transition from page one to page two. Page count alone will not detect a missing page replaced by a duplicate.
Use annotations to guide attention
Show the Markup toolbar and choose a text, shape or note tool appropriate to the request. An arrow can direct a reviewer toward one figure; a text box can add a short label when a form is not fillable. Avoid covering the original instructions. On a form, try clicking the intended field first: a real form field is preferable to an improvised text box when it works.
Use one annotation color and make the meaning explicit. In a draft review, a yellow highlight might mean “please check this figure,” but the recipient cannot infer that convention without a note. A finished application packet generally should not contain your internal review comments at all. Read it once as the recipient, rather than as the person who knows what every mark was meant to do.
| Need | Appropriate action | What to check afterward |
|---|---|---|
| Change page sequence | Move thumbnails | All pages remain, in the intended order |
| Point out a question | Note or short annotation | Comment is readable and its purpose is clear |
| Fill an ordinary blank | Form field, or a text box if necessary | Text fits and does not obscure labels |
| Remove confidential PDF text | Preview's Redaction tool on a copy | Redaction is applied and sensitive content is absent |
| Hide an accidental private screenshot | Replace or recapture the image | Private material is absent from the source being sent |
A black rectangle is not secure redaction
A shape drawn over text is an annotation. It can leave the underlying text accessible or removable. If you need to redact an ordinary PDF in Preview, use the actual Redaction tool, read its warning and mark the relevant text or areas. Apple explains that redactions become permanent when the document is closed. Work on a duplicate because this is deliberately destructive.
After closing and reopening the copy, inspect every redacted page. Try searching for the removed phrase and selecting the surrounding text. These checks can catch an obvious failure but are not a certification of a complex PDF's security: attachments, hidden content or material elsewhere in the packet may need separate handling. For particularly sensitive documents, obtain the recipient's approved submission method and prepare only the necessary information in the first place.
Save, reopen and test the actual deliverable
Name the output for its purpose, for example Workshop application packet.pdf. Save the working document, close it and reopen the file from Finder. This matters when several similar Preview windows are open: the window you inspected may not be the file attached to your message. Check page count, orientation, visible comments, form text and any promised redactions in that reopened file.
If a recipient requires a maximum size, use Finder's Get Info to inspect the output before sending. Aggressive compression can make a scanned reference unreadable, so compare the smallest text after any size reduction. A modest file that a reviewer can read is better than a tiny one that has lost the details the application depends on.
When the packet refuses to cooperate
If a PDF will not accept changes, inspect whether it is locked or restricted rather than repeatedly exporting it. If text boxes move or fonts change after sharing, test the saved PDF in another viewer and distinguish an editable working document from the final visual copy. If pages disappear, return to the untouched inputs and rebuild only the affected part. A duplicate source folder makes this recovery a short operation instead of an exercise in reconstruction.
For a document that is still being written, fix its structure in Pages before making a PDF. For paper inputs, start with a legible document scan. Preview is most useful at the assembly and inspection stage, after the words and source pages are already dependable.
Sources & further reading
Apple’s documentation supports the feature details. The scenarios and decision sequences above are CJVV’s editorial guidance.