WebFV
PdfCraft / Field guide

Combine, reorder and verify your first PDF

Use two harmless sample files and verify the saved output, not just a success message.

By WebFV Editorial · Checked October 21, 2026 · PdfCraft CLI 0.10.1 · macOS

What the evidence coversExecuted: combine, reorder, write, reopen, page count and extracted text. Desktop UI and hosted-web saving were not tested.

The result we are checking

This workflow combines two one-page PDFs, moves the second page to the front, writes a new file and reopens it. The expected result is two pages, BETA first and ALPHA second. We tested these commands with the official macOS universal PdfCraft CLI 0.10.1.

The test uses ordinary text pages, not forms, scanned documents, encrypted files or digital signatures. It establishes this small workflow on this version. It does not establish full Acrobat compatibility or the behavior of the desktop and hosted-web interfaces.

1. Get the harmless inputs

Download alpha.pdf and beta.pdf into an empty working directory. They contain only the visible labels ALPHA and BETA. Keep both source files unchanged so you can compare the final output.

Get the CLI from the official release, following the download guide. The commands below assume pdfcraft-cli is on your PATH. Otherwise, invoke it with the full path to the extracted executable.

Before editing, inspect each source:

pdfcraft-cli info alpha.pdf
pdfcraft-cli info beta.pdf

Each should report one page. If you are using your own files instead, write down the expected number of pages and a distinctive label from each. Do not use a confidential client document for your first installation check.

2. Combine in a known order

pdfcraft-cli combine alpha.pdf beta.pdf --out combined.pdf

The command's input order is the intended document order: ALPHA, then BETA. Open combined.pdf or inspect it with info and text before changing anything else. This intermediate check helps separate a combine problem from a later move problem.

Always use a new output filename for a first test. A successful operation should leave both source PDFs available. For complex documents, compare bookmarks and form fields as separate acceptance criteria; a correct page count alone cannot establish that every document feature survived.

3. Move page two to the front

pdfcraft-cli edit combined.pdf --out reordered.pdf --move 2:1

The tested CLI accepts one-based page numbers here. The move takes page two and places it at position one. Do not assume another tool's zero-based numbering applies. When chaining multiple edits, page numbers refer to the document after preceding operations; split a complex sequence into inspectable steps first.

The output is a new file. The original combined.pdf remains your comparison copy. If a command exits with an error, preserve its message and inspect whether an output file was actually written before rerunning against the same path.

4. Reopen and inspect the saved file

pdfcraft-cli info reordered.pdf
pdfcraft-cli text reordered.pdf

Our info output reported pages: 2. The extracted text was BETA, a page separator, then ALPHA. These commands start a new process and read the saved file from disk, so the check is more meaningful than inspecting only an in-memory editing state.

Check Expected Observed in this test
Source page counts One each One each
Output page count Two Two
First page label BETA BETA
Second page label ALPHA ALPHA
Reopen persisted output Readable Read successfully by a new CLI process
Desktop UI / hosted web save Separate test required Not tested

You can download the expected reordered PDF to compare. For your real document, also open the result in an independent viewer and inspect its layout. Text extraction proves text order, not visual fidelity for all fonts or graphics.

If Save says success but the file is wrong

First identify the interface and version. A terminal command, native desktop save dialog and hosted-web download bridge are different paths. Confirm the output filename, its modification time, and whether reopening that exact file shows the change.

Issue 2167 reports a hosted-web save problem involving a host bridge and download behavior. It is a source-specific report, not proof that every current PdfCraft build loses changes. Our CLI test does not reproduce or resolve that hosted-web report.

If your file is missing or unchanged, preserve the original, capture a sanitized error and test with these public samples. That produces a much safer bug report than uploading a private PDF. State whether the failure occurred while combining, moving, saving or reopening.

Next step

Repeat the same acceptance pattern on a copy of a representative document: expected pages, intended order, write to a new path, reopen, inspect text and layout. Add checks for forms, comments and signatures only when those features matter to your document. Do not infer their preservation from this two-page test.

Source: PdfCraft CLI and automation documentation. Test date: October 21, 2026.