Skip to main content
BentoPDF supports custom branding through build-time environment variables. You can replace the default logo, application name, and footer text with your own — without modifying source code. Branding works in both full mode and Simple Mode, and can be combined with other build-time options like BASE_URL, SIMPLE_MODE, and VITE_DEFAULT_LANGUAGE.

​
Environment variables

VariableDescriptionDefault
VITE_BRAND_NAMEBrand name shown in the header and footerBentoPDF
VITE_BRAND_LOGOPath to your logo, relative to public/images/favicon-no-bg.svg
VITE_FOOTER_TEXTCustom footer or copyright text© 2026 BentoPDF. All rights reserved.
Branding variables are baked into the JavaScript bundle at build time. Changing them after the image is built has no effect. You must rebuild to apply new branding.

​
How to apply custom branding

Pass branding variables as Docker build arguments:
docker build \
  --build-arg VITE_BRAND_NAME="AcmePDF" \
  --build-arg VITE_BRAND_LOGO="images/acme-logo.svg" \
  --build-arg VITE_FOOTER_TEXT="© 2026 Acme Corp. Internal use only." \
  -t acmepdf .
Then run the image:
docker run -p 3000:8080 acmepdf
Place your custom logo file in the public/ folder before building. For example, if your logo is at public/images/acme-logo.svg, set VITE_BRAND_LOGO=images/acme-logo.svg.

​
Combining with other options

You can use branding variables together with other build-time configuration. For example, to deploy to a subdirectory with Simple Mode and a custom language: 
docker build \
  --build-arg VITE_BRAND_NAME="AcmePDF" \
  --build-arg VITE_BRAND_LOGO="images/acme-logo.svg" \
  --build-arg VITE_FOOTER_TEXT="© 2026 Acme Corp. Internal use only." \
  --build-arg SIMPLE_MODE=true \
  --build-arg BASE_URL=/pdf-tools/ \
  --build-arg VITE_DEFAULT_LANGUAGE=fr \
  -t acmepdf .

Build docs developers (and LLMs) love

Get started for freeTalk to us