Deploy BentoPDF on networks with no internet access. Bundle WASM files, OCR assets, and the Docker image with the included prepare-airgap.sh script.
For networks with no internet access — government, healthcare, financial, or other security-sensitive environments — BentoPDF can be deployed entirely offline.
BentoPDF’s WASM module URLs are baked into the compiled JavaScript at build time. When a user opens the app, their browser fetches those WASM files at runtime from whatever URL was configured during the build. Docker does not download WASM files during the image build.For an air-gapped deployment you need to:
On a machine with internet: download the WASM packages, build a Docker image configured to point at your internal server, and bundle everything together.
Transfer the bundle into the isolated network via USB drive, internal artifact repo, or other approved method.
On the air-gapped side: extract the WASM files to your internal web server, load the Docker image, and run the container.
Same-origin requirement. WASM files must be served from the same origin as the BentoPDF app. Web Workers use importScripts(), which cannot load scripts cross-origin. If BentoPDF runs at https://internal.example.com, the WASM base URL must also be https://internal.example.com/wasm (not a different host).
The included prepare-airgap.sh script automates the entire preparation process: it downloads all WASM packages, builds the Docker image with your internal URLs, exports everything, and produces a self-contained bundle with a setup script.
git clone https://github.com/alam00000/bentopdf.gitcd bentopdf# List supported OCR language codesbash scripts/prepare-airgap.sh --list-ocr-languages# Search OCR language codes by namebash scripts/prepare-airgap.sh --search-ocr-language german# Interactive mode — prompts for all optionsbash scripts/prepare-airgap.sh# Fully automatedbash scripts/prepare-airgap.sh --wasm-base-url https://internal.example.com/wasm
Where WASM files will be hosted internally. This sets the base for all WASM and OCR URLs.
(required; prompted if missing)
--image-name <name>
Docker image tag
bentopdf
--output-dir <path>
Output bundle directory
./bentopdf-airgap-bundle
--simple-mode
Enable Simple Mode
off
--base-url <path>
Subdirectory base URL (e.g. /pdf/)
/
--language <code>
Default UI language (e.g. fr, de)
(none)
--brand-name <name>
Custom brand name
(none)
--brand-logo <path>
Logo path relative to public/
(none)
--footer-text <text>
Custom footer text
(none)
--ocr-languages <list>
Comma-separated OCR language codes to bundle (e.g. eng,deu,fra)
eng
--list-ocr-languages
Print all supported OCR codes and names, then exit
off
--search-ocr-language <term>
Search OCR codes by name or abbreviation (e.g. search german)
off
--dockerfile <path>
Dockerfile to use
Dockerfile
--skip-docker
Skip the Docker build and export step
off
--skip-wasm
Skip WASM download (reuse existing .tgz files)
off
At the interactive prompt, type list to print all Tesseract language codes or search <term> to find a match — for example search chi for Chinese variants.
Copy the entire bentopdf-airgap-bundle/ directory into the air-gapped network via USB drive, internal artifact repository, or another approved transfer method.
2
Run the setup script
On the air-gapped machine:
cd bentopdf-airgap-bundlebash setup.sh
The setup script:
Loads the Docker image from bentopdf.tar
Extracts all WASM packages to the directory your web server will serve
Optionally starts the container
3
Verify
Open the app URL in a browser and run a PDF operation that requires a WASM module (e.g., PDF/A conversion). If the WASM files are not accessible, the browser console will show a failed fetch for the configured URL.
For fully offline searchable PDF output (OCR with a text layer), BentoPDF needs to load NotoSans font files to embed into the PDF. Without VITE_OCR_FONT_BASE_URL, the app will try to fetch them from public Google Fonts CDN URLs.Set VITE_OCR_FONT_BASE_URL to the internal directory serving the bundled ocr-fonts/ contents:
