How do you build and organize a PDF without losing a page?

What should the finished PDF contain?

Before editing, describe the finished packet in plain language: cover, application, invoice, receipt and appendix; or perhaps only pages 4–7 from a larger report. This small step separates document structure from tool operations. It also makes omissions easier to notice later.

Keep an untouched source copy. If you are starting with photographs or screenshots, keep those originals too. A PDF operation can be technically successful while the resulting packet is still wrong because a source page was cropped, rotated incorrectly, duplicated or placed in the wrong position.

Build a page map before page numbers start moving

PDF tools usually work with physical positions in the file, while a document may print its own page numbers inside the page. A cover and contents sheet can make printed page 1 the third physical page. SnakTool page selections refer to positions in the input PDF, starting at 1.

Write a short map for any packet where a mistake matters. For example: 1 cover, 2 summary, 3 invoice, 4 receipt, 5 duplicate receipt, 6 appendix. If position 5 is deleted, the appendix becomes position 5 in the new file. Any later operation must use the new document's positions.

Starting from images changes the first half of the workflow

When the source is a set of JPG or PNG files, page order is created before the PDF exists. Do not trust filename sorting blindly: page-1, page-10 and page-2 may not appear in the human order you intended. Review the selected-file list and arrange it explicitly.

Normalize orientation before assembly. A phone can display a JPEG upright because it honors orientation metadata even when the encoded pixel matrix is rotated. JPG-to-PDF embeds the encoded image dimensions without using EXIF orientation as a layout instruction, so save a normalized image first when orientation matters.

Crop unrelated surroundings only when they are genuinely unnecessary. If the image is evidence, a receipt or an official record, keep an uncropped original. Packaging an image inside a PDF does not restore blurred text, recover clipped edges or turn photographed words into selectable text.

1. Keep the original images and identify the intended reading order.
2. Normalize sideways images and crop only deliberate unwanted margins.
3. Choose one accepted input route and arrange the files.
4. Create the PDF, then inspect every page boundary before further edits.

• Assemble JPG images
• Assemble PNG images
• Rotate an image before assembly

Image dimensions become PDF page dimensions

SnakTool maps image pixels to PDF points using 96 pixels per inch and 72 points per inch. A 960 × 640 image therefore becomes a 720 × 480 point page. The page follows the image proportions; the converter does not silently place every image on A4 or Letter paper.

That means portrait and landscape pages can coexist in one packet and differently sized images can create differently sized PDF pages. This is often fine for on-screen sharing. If a recipient requires exact paper size, uniform margins or a designed print layout, prepare the sources for that requirement rather than assuming image pixels imply a paper format.

Input

Three normalized images: 960×640, 1200×1600 and 960×640

Method

Arrange them in reading order and convert each image to one PDF page

Result

A three-page PDF whose page proportions follow the three source images

Choose the page operation by what should survive

Rotation changes orientation without choosing a new reading sequence. Deletion keeps everything except selected pages. Extraction does the opposite: it creates a new PDF from selected pages. Reordering describes the complete sequence that should remain. Merge combines complete source PDFs in the order you provide them.

These operations can overlap in what they appear to achieve, but their intent is different. If you only need pages 3–5, extraction is easier to review than deleting every other page. If every page must remain but two are swapped, reorder instead of rebuilding the document.

Do not reuse an old page map after a structural edit

Deleting, extracting or reordering changes positions. Finish one structural operation, open its result and make the next page map from that result. Printed page labels inside the content do not automatically update, so a page marked “12” may occupy a completely different physical position.

Repeated or overlapping selections can also make intent ambiguous. Prefer a simple explicit selection that another person could read and verify. When making several separate attachments, run extraction for each intended output rather than assuming one extraction creates a ZIP of individual pages.

The last review is about meaning, not only page count

A ten-page result is not correct merely because the source also had ten pages. Inspect the first page, last page and every boundary you edited. Zoom into small text on photographed pages. Confirm that landscape pages are readable and that no private adjacent page followed an extracted page into a shareable file.

Forms, annotations, bookmarks and digital signatures deserve separate checks. Rewriting a PDF can affect advanced document features, and a modified file does not preserve the validity of a signature over the original bytes. Keep the original whenever those features matter.

• Count pages and compare them with the planned packet.
• Check order using page content, not printed numbers alone.
• Inspect every rotated, removed, extracted or moved boundary.
• Open the downloaded result before replacing or sending anything.
• Keep the untouched source until the recipient accepts the final file.