PDF Checker
Detect PDF Errors Before They Affect Business
Identify potential PDF problems before they enter your workflows. Flag issues with compression, fonts, JS objects, user data, images and more.
Detect & Analyze Errors
Find issues with compression, fonts, JS objects, user data, images and more.
Batch Processing
Check large numbers of PDFs & flag before they enter your document workflow.
Customization
Create custom validation programs with JSON.
Compliance
Make sure documents meet PDF/A compliance when necessary.
Pair with PDF Optimizer
PDF Optimizer can process documents based on conditions reported by PDF Checker.
Easy to Use
Simple command line application for 64-bit Windows and Linux platforms.
Get Free Trial
Command Line Syntax
Command Line Syntax
//The command syntax for PDF Checker includes these values:
Required: The executable name, pdfchecker
Required: -i [--input] name and path of the PDF input file to review
Required: -j [--profile] name and path of the JSON profile file
Optional: -o [--output] name and path to assign to the output results file
Optional: -s [--json-output] name and path to assign to a JSON output results file
Optional: -p [--password] password needed to open a protected PDF input file
Optional: -n [--nopath] remove the system paths to the input PDF or JSON file
//The command syntax for PDF Checker with the required values looks like this:
pdfchecker –-input test.pdf –-profile everything.json
//The full command syntax for PDF Checker looks like this:
pdfchecker –-input test.pdf –-profile everything.json --output PDFChecker_results.txt –-password mypassword --nopath
//To export the output to a JSON file looks like this:
pdfchecker –-input test.pdf –-profile everything.json –-json-output PDFChecker_results.json –-password mypassword --nopath
//To create both kinds of output files, text and JSON:
pdfchecker –-input test.pdf –-profile everything.json –-json-output PDFChecker_results.json –-output PDFChecker_results.txt
//To display the JSON output on your console and save the same output as a text file:
pdfchecker –-input test.pdf –-profile everything.json –-json-output - –-output PDFChecker_results.txt
//To display the text output on your console and save the same output as a JSON formatted file:
pdfchecker –-input test.pdf –-profile everything.json –-output - --json-output - PDFChecker_results.json
//If you need to provide the path as well as the file name:
pdfchecker –-input C:\Datalogics\CheckerFiles\AnnualReport2016.pdf –-profile everything.json –-output C:\Datalogics\PDFChecker_results.txt
//If any of the file or path names include spaces, use quotes around the name for example:
pdfchecker –-input C:\Datalogics\CheckerFiles\AnnualReport2016.pdf –-profile everything.json –-output "C:\Datalogics\PDFChecker results.txt"
//Provide a path name for the JSON profile file, just as you would for the input PDF document and the output results file:
pdfchecker –-input C:\Datalogics\CheckerFiles\AnnualReport2016.pdf –-profile C:\Datalogics\JSONProfiles\everything.json –-output C:\Datalogics\PDFChecker_results.txt
//If you don’t enter a path name for the JSON profile file as part of the "-j" (or --profile) value, PDF Checker will look for the JSON profile file to use. It will first search the CheckerProfiles folder, which is part of the directory structure for your PDF Checker software installation package and where the standard JSON Profile file, everything.json, the file we provide with the software, is stored. If the file is not in the CheckerProfiles directory, PDF Checker will treat the "-j" input value in the command statement as a path to the profile, and try to load the profile from that location.
//This makes the product easier for you to use after you install it. All you need to do is provide the name of the JSON Profile file. PDF Checker can find the file for you.
//You can use the JSON profile we provide, everything.json, from the command line, like this:
pdfchecker –-input test.pdf –-profile everything.json --output PDFChecker_results.txt –-password mypassword --nopath
