Install Oobee manually
What a manual installation involves
A manual installation sets up the tools that the portable Oobee bundles: Node.js to run Oobee, a Java runtime for VeraPDF, and VeraPDF to scan PDF files. Use it when you cannot use the portable download, for example on Linux or on a managed machine where you control the tool versions.
To use the portable download, refer to Install the portable Oobee.
Prerequisites
- A computer with Google Chrome installed. On Linux without Chrome, Oobee uses Playwright’s Chromium instead. Install it with
npx playwright install chromiumafter Step 4. - The Oobee source code, from the Oobee repository on GitHub.
- Internet access to download the tools and the npm packages.
- Permission to install software and to edit your
PATHenvironment variable.
Step 1: Install Node.js
Oobee requires Node.js 20 (LTS) or later. Check your version:
node -vIf Node.js is missing or older than 20, install it. To manage Node.js versions, use Node Version Manager (NVM):
nvm install --lts
nvm use --ltsRun nvm use --lts again each time you open a new terminal.
Step 2: Install Java
Oobee requires a Java Runtime Environment (JRE) or Java Development Kit (JDK) 11 or later. Check your version:
java --versionIf Java is missing, install the Corretto distribution of OpenJDK.
Step 3: Install VeraPDF
Oobee uses VeraPDF to scan PDF files. Follow the VeraPDF install guide. You can use its automated installation script and set the <installpath> value in the XML file to a location you choose. The repository includes example files, scripts/verapdf-auto-install-macos.xml and scripts/verapdf-auto-install-windows.xml.
Install VeraPDF, add it to your PATH, then check it:
./verapdf-install ./auto-install.xml
export PATH="<VERAPDF_LOCATION>:$PATH"
verapdf --versionOn Windows, use vera-install.bat instead of vera-install. Add VeraPDF to your PATH again each time you open a new terminal, unless you set it permanently.
Step 4: Install the packages and build Oobee
Clone the Oobee repository, or unpack a copy of it, and open the project folder in a terminal. Then run:
npm install
npm run buildnpm run build copies the report templates and compiles the TypeScript source into the dist folder. Oobee does not start until you run it.
Step 5: Start Oobee
Start the interactive scan:
npm startOobee prints a banner with its version and asks “What would you like to scan?”. To scan with command-line options, refer to Run a scan.
Constraints and limitations
| Constraint | Detail |
|---|---|
| Node.js version | Node.js 20 or later. Older versions cause a syntax error on start. |
| Java version | Java 11 or later, needed only for PDF scans. |
| Build after changes | Run npm run build again after you change the source or pull new code. A stale dist folder keeps old behaviour. |
| Switching Node.js versions | If you switch versions, run npm rebuild or npm install to fix “compiled against a different Node.js version” errors. |
Related content
- Run a scan — choose a scan type and options.
- CLI options, environment variables and error codes — optional settings.
- Troubleshooting — fix start-up errors.