You can handle this directly in your browser with our free pdf to images tool — nothing gets uploaded.
You just got back from a copy shop with a box of scanned pages, or you have spent the evening scanning a large document with your phone. The result is a folder full of PDFs named something like "scan_0001.pdf", "IMG_4032.pdf", "page_scan.pdf" - names that tell you nothing about where each file belongs in the final order. If you try to merge them now, you will likely produce a document with pages in the wrong sequence, and fixing that means starting over.
This article walks through a practical naming convention, why the order of digits matters more than most people expect, and a repeatable process for sorting, verifying, and merging a 100-file folder in roughly ten minutes without losing your mind.
A file name is the only piece of metadata you reliably carry from scan to merge. Once the files are on disk, the order you scanned them is lost unless you encoded it in the name. The convention I recommend is:
YYYY-MM-DD_seq_descript.pdf
A finished folder might look like this:
2026-03-12_001_lease.pdf
2026-03-12_002_lease.pdf
2026-03-12_003_lease.pdf
2026-03-12_040_receipts.pdf
2026-03-12_041_receipts.pdf
If you are dealing with several unrelated documents in the same folder, the descript token is what keeps them separated when you sort by name. If everything is one document, you can drop descript and just keep YYYY-MM-DD_seq.pdf.
The whole point of the pattern is that a plain alphabetical sort of the file names gives you the correct reading order for free. No manual reordering, no spreadsheet, no remembering which stack was which.
This is the mistake people hit most often. If you name files 1.pdf through 100.pdf without zero-padding, an alphabetical sort produces:
1.pdf, 10.pdf, 100.pdf, 11.pdf, 12.pdf, 2.pdf, 20.pdf, and so on.
The digit 1 is smaller than 2 in character terms, so 10, 100, and 11 all jump ahead of 2. Every file system, every merge tool, every sort-by-name dialog in Windows or macOS will hand you this broken order.
Zero-padding fixes it because now the sort compares digit by digit:
001.pdf, 002.pdf, 003.pdf, 010.pdf, 011.pdf, 100.pdf
001 comes before 002, and 010 comes after 009, exactly as you want. Use three digits as a default - it fits any batch up to 999 pages. If your batch is going to be longer, use four digits. The padding width must be chosen before you start, and it must cover the largest sequence number you will ever need. You cannot add padding to files that already exist without renaming them all.
Here is the concrete workflow I use for a 100-page batch that just came back from a copy shop. Total time, including verifying the order, is about ten minutes once the files are on disk.
Step 1 - Drop the files into one folder. Do not let the copy shop send you a zip with nested subfolders if you can help it. One flat folder, 100 files, is the state you want to work in.
Step 2 - Check the existing names. Most phone scanners and copy-shop output will give you sequential but ugly names like IMG_001 through IMG_100, or scan_01 through scan_100. The good news: even ugly sequential names are still a valid sort key as long as they are zero-padded and in order. If the shop gave you scan_1 through scan_100 with no padding, you have the 1-versus-10 problem and you must rename before anything else.
Step 3 - Rename to your target pattern. On Windows, open File Explorer, select all files, press F2 on the first file, type 2026-03-12_001_lease, and press Tab. Windows will automatically continue the sequence for the remaining 99 files. On macOS, use Finder's built-in rename dialog, which also continues numeric suffixes, or use a bulk rename tool. If your tool does not continue sequences, a one-line script does the job: iterate over the folder in sorted order of the current names, and rename each file to the new pattern with a zero-padded index formatted to three digits. The key detail is that you sort by the current ugly name and write out the new zero-padded name, so the new order is correct for the next sort.
Step 4 - Verify with a plain list. Sort the folder by name in your file manager and scroll through. You are checking two things: the sequence is 001, 002, 003 with no gaps and no duplicates, and the visual content of the first and last few pages matches what you expect, such as a title page and an end page. For a 100-file folder, this visual check takes under a minute.
Step 5 - Spot-check the middle. Open file 050, file 051, and file 052. If the content is continuous across those three, the middle of the batch is almost certainly fine. If something is off, the error is localized and you only have to fix a small window, not the whole folder.
That is the ten minutes: rename in two, verify in two, spot-check in one, and the remaining time is free for the merge.
The worst moment to discover a swapped page is after you have merged 100 pages into a single large PDF and you have to split it back apart. Two habits prevent that.
The thumbnail sweep. Open the folder in thumbnail view or in a PDF reader that shows a filmstrip. Scroll through once at a brisk pace, looking only for visual breaks - a page that is blank where content should be, a page that is upside down, a page that is clearly from a different document. You do not need to read anything. You are looking for anomalies, and anomalies stand out against a consistent batch. This sweep takes about two minutes for 100 pages and catches most of the problems.
The boundary check at every document transition. If your batch contains three sub-documents, such as a lease, receipts, and a contract, the most likely place for an out-of-order page is the boundary between them - the last page of the lease and the first page of the receipts. Open the files around that transition and confirm the content actually switches there. Boundaries are where a scanner operator is most likely to have grabbed the wrong stack.
A one-line integrity check. Print the file names and their sizes to a text file and compare against the list the copy shop gave you, if they gave you one. A missing file shows up as a gap in the sequence; an extra file shows up as a duplicate. You can also run a quick hash script that walks the sorted folder, computes a short hash and the file size for each PDF, and prints them in order. If you have a manifest with file sizes from the shop, comparing sizes alone is enough to catch missing or extra pages. You do not need full hashes unless you are auditing against a previous scan.
The key principle is to verify the order while the files are still separate. Once merged, your only path back is splitting, and splitting a 100-page PDF into 100 single-page PDFs is a slow, error-prone operation you do not want to do twice.
A tempting shortcut is to merge everything into one big PDF first, then rename the pages, then split back out. This is the wrong order, and here is why.
When you merge, the page numbers in the combined file are assigned by the merge tool in the order you fed it the files. If your input files were in the wrong order, the merged PDF has the wrong page order baked in. To fix it, you must now split the merged PDF into 100 single-page PDFs, rename them, re-sort, and re-merge. You have done twice the work for no gain, and every split-and-remerge cycle risks a tool dropping a page or changing the file size, which makes a subsequent integrity check harder because you no longer have the original file to compare against.
The correct order is always to rename and sort first, then merge. The merge is the last step, not the first. If you find an out-of-order page after merging, do not try to reorder pages inside the merged PDF with a PDF editor - that creates a new file with new internal structure and new file sizes, and you lose your ability to verify against the original batch. Instead, split back to the original single-page files, fix the two or three bad files, and re-merge. The split-and-remerge is a quick operation if you have good tooling; it is a long, painful operation if you did not keep the original single-page files handy. So keep them. Do not delete the batch folder until the final merged PDF has been verified page by page.
Once the folder is renamed, verified, and spot-checked, the merge is mechanical. From the command line, a simple loop or a batch tool that merges all PDFs in sorted name order does the job. The important detail is that the merge input is sorted by the zero-padded file name before any merging happens. If your merge tool has a sort-by-name option, use it; if you are invoking a command-line tool, pipe the file list through a sort first so the glob expansion does not matter. After the merge, open the result and confirm the page count matches your batch, then flip to the first, middle, and last pages to confirm the content is where you expect. Archive the original batch folder afterward; do not delete it until the merged file is verified.
The entire discipline comes down to four rules. First, choose a naming pattern where alphabetical sort equals reading order, and commit to it before you start. Second, zero-pad the sequence number to a width that covers your longest batch, because unpadded numbers break every sort. Third, verify the order while the files are still separate - thumbnail sweep, boundary check, size or hash check - and only then merge. Fourth, keep the original batch folder until the merged file is verified, because the only way to fix a bad merge is to split it back into the files you still have.
Do it in that order and a 100-page batch goes from a box of scans to one clean merged PDF in about fifteen minutes, with no page lost and no page out of place.
Related reading: annual review scan reconcile paper records, batch ocr scanned pdfs, car repair records scan before selling.
How do I rename multiple scanned PDFs at once?
Use the bulk rename feature to apply a pattern. Input a base name and add a dynamic counter suffix, like 'Scan_001.pdf'. This automatically numbers files sequentially. Ensure the pattern uses zero-padded numbers to maintain alphabetical sorting order during the merge process.
What is the best way to sort PDFs before merging?
Enable the custom sort option in the tool interface. You can reorder files by dragging them into the desired sequence or by sorting based on specific metadata tags. This step is critical because the merge tool processes files strictly in the order they are listed in the queue.
Does the tool support custom filename patterns?
Yes, you can define custom patterns using variables. Insert the current date, page count, or a custom string alongside the counter. For example, use 'Invoice_{DATE}_{INDEX}.pdf' to automatically timestamp each file. This helps organize archives without manual editing of individual files.
Can I preview the final merge order?
Absolutely. After renaming and sorting, use the preview panel to visualize the sequence. This allows you to spot misordered documents or duplicate files before committing. Once you confirm the order is correct, click the merge button to generate the single PDF file.