This page is a disclosed PDFZUS-owned editorial case study. It is not an independent review, a Pokémon TCG Pocket meta ranking, or a promise that any third-party tool is permanently private. The useful output of a PDFZUS Pokémon Card Workflow is a reproducible archive other people can repeat and audit: masters kept intact, stable names, current privacy wording checked on the provider’s own pages, and a merged PDF that has been opened and inspected.
Preserving scans, choosing filenames, checking privacy claims, and validating a merged PDF are a reproducible document workflow. That sentence is the decision rule for this article. If a step cannot be explained to someone else with a date, a file path, and a pass/fail check, it is not ready for a shared archive.
What this workflow is for
Collectors and editors often need one PDF that shows a card’s front and back in order, or a short sequence of scans for a set note. The temptation is to merge first and delete the originals later. Archival digitization guidance from FADGI and personal-archiving advice from the Library of Congress push the opposite order: keep the highest-quality capture you already have, treat the PDF as a convenient derivative, and verify integrity after export.
A PDFZUS Pokémon Card Workflow therefore has four jobs:
- Preserve original scans before rotation, crop, recompression, or assembly.
- Name files so a stranger can reconstruct page order months later.
- Read the live privacy and terms pages before you process sensitive images.
- Open the downloaded PDF and confirm page count, order, readability, and a second backup.
Use PDFZUS when you want a browser-based merge or images-to-PDF path that the provider currently describes as local WebAssembly processing. Use this site’s card catalog, set index, and pack index when you need TCG Pocket entity pages—not as substitutes for the document workflow.
Preserve masters before you edit
Save a masters/ copy of every scan before you straighten, crop, color-correct, or feed files into a merge tool. If the scanner only produced JPEG, keep that exact JPEG; do not re-save it as another lossy file and call it a lossless master. FADGI’s technical guidelines distinguish production masters from access derivatives; NARA’s raster guidance makes the same separation for identifiers, naming, and quality control.
A practical starting resolution for testing legibility of small card text is around NARA’s enhanced-scan figure of 400 ppi at original document size. That is a test target, not a universal Pokémon-card rule and not a PDFZUS product requirement. Choose resolution from the smallest detail that must remain readable—set symbol, collector number, foil microtext—then stop raising DPI once those details survive on a second device.
Never delete masters after a successful merge. The PDF is the reading copy; the scans are the recovery path when a page is rotated wrong, clipped, or compressed too hard.
Filename scheme that survives handoff
Stable names beat clever names. NARA’s naming conventions favor lowercase ASCII, digits, hyphens or underscores, no spaces, and one extension period. Library of Congress personal-archiving notes add descriptive structure and an inventory that holds metadata the filename cannot carry.
Use a fixed field order:
<set>_<card-number>_<variant>_<side>_<capture-date>_<sequence>_<role>.<ext>
Example: a1_150_mewtwo-ex_front_20260804_01_master.jpg
Keep a simple manifest (CSV or plain text) with columns for path, SHA-256 checksum, page role, expected PDF page number, and notes. NDSA fixity guidance and the Digital Preservation Coalition checksum handbook treat checksums as change detectors: compute them when masters are frozen, recompute after transfer, and treat a deliberate migration as a new baseline. Prefer SHA-256 for new personal manifests rather than MD5.
Check privacy claims on the dated pages
PDFZUS currently states on its home and tool pages that document merge and conversion can run locally in the browser without uploading the document content. That is a first-party product claim. It is not an independent security audit, a GDPR certification, or proof of zero network activity.
Before you process private collection photos or identity-adjacent paperwork:
- Read the current privacy policy (dated 20 September 2025 on the research pass) for metrics, storage, error reports, and rights language.
- Read the current terms of service for supported inputs, warranties, and file-size caveats.
- Use the support page for ordering, export behavior, and troubleshooting wording that can change independently of marketing copy.
German and EU transparency materials from BfDI and the official GDPR text are useful framing for what “current verification” means: look for who collects what, for which purpose, with which legal basis, and how long data is kept. Do not endorse labels such as “DSGVO compliant,” “HIPAA,” “CCPA,” or “end-to-end encrypted” unless you have independent evidence. Local processing can reduce exposure; it does not by itself prove legal compliance.
If the workflow matters for sensitive material, assume policies can change after this article’s 2026-08-04 review date and re-open the provider pages yourself.
Merge, then validate the PDF
A concrete PDFZUS Pokémon Card Workflow for card scans looks like this:
- Copy scans into
masters/and compute checksums. - Create working copies only if you must rotate or crop; leave masters untouched.
- Order pages visually—front before back, then the next card—using the PDFZUS merge or images-to-PDF path.
- Export/download the PDF to a known folder with a dated name.
- Re-open the downloaded file. Confirm expected page count, order, orientation, no duplicates or missing sides, unclipped edges, and readable small text.
- Open the same file in a second maintained viewer when feasible. Mozilla’s PDF.js is a useful interoperability smoke check; it is not a PDF/A validator.
- Copy the validated PDF and the
masters/folder to a second location. Library of Congress personal-archiving guidance still recommends at least two copies in different places and periodic readability checks.
If page order is wrong, split and rebuild with the PDF splitter or re-order with the page organizer rather than accepting a “close enough” archive. If you need a smaller file, inspect every page after compression: raster fall-backs can erase the text you scanned to preserve.
PDF/A is optional. A .pdf extension is not a preservation profile. Only claim PDF/A when you deliberately convert and validate with a suitable tool such as veraPDF. Visual comparison with the masters still matters more than a conformance badge for a personal card binder PDF.
Failure cases and decision rule
The workflow fails when:
- Masters were overwritten by the edited copies.
- Filenames cannot reconstruct front/back order without tribal knowledge.
- Privacy claims were copied from an old blog post instead of the live policy.
- The PDF was never opened after download, so page 3 is upside down in every backup.
- The only copy lives on one laptop disk.
Decision rule: ship the archive only when a second person (or your future self with no memory of the session) can find the masters, explain the names, cite the privacy pages checked, and verify the PDF page list against the manifest.
FAQ
Do I need PDFZUS to follow this article?
No. The reproducibility rules apply to any tool. This case study links PDFZUS because the page is a disclosed PDFZUS-owned editorial workflow and because the provider’s current pages document a local merge path you can inspect yourself.
Should I delete scans after the PDF looks good?
No. Keep masters. The PDF is the convenient reading copy.
Is local processing the same as “fully offline forever”?
No. First visits still load site assets. Provider pages also describe metrics, storage, and optional reporting. Separate “document content stays on device” from “the site never talks to a server.”
When should I chase PDF/A?
Only when a recipient or archive policy requires a validated profile—and only after you still pass the visual QC against masters.
Sensible next steps
- Start from PDFZUS and verify the live privacy and terms pages before sensitive use.
- Browse this site’s card catalog when you need localized card names for filenames.
- Use the set index and pack index when a scan batch is organized by expansion rather than by single cards.
- Compare deck samples on the deck archive only if you are naming files after a competitive list—this article does not rank decks.
Sources and live checks
- PDFZUS home for the current merge entry point and local-processing claims
- PDFZUS support for ordering, export, and troubleshooting
- PDFZUS privacy policy and terms of service for policy wording that can change independently of this article
- PDFZUS images-to-PDF, page organizer, and splitter for repair paths
- FADGI, NARA, Library of Congress, NDSA, DPC, NIST, BfDI, and ISO/PDF Association materials listed in the research ledger for preservation, naming, fixity, and privacy-framing evidence
Data window for this editorial refresh: 2026-08-04 (Asia/Shanghai). Re-check provider pages before any sensitive batch.
