- PHP 5.0+ with the DOM extension enabled. Note that the domxml PECL extension conflicts with the DOM extension and must be disabled.
- Some fonts. PDFs internally support Helvetica, Times-Roman, Courier, Zapf-Dingbats, & Symbol. DOMPDF adds the , but if you wish to use other fonts or Unicode charsets you will need to install some fonts. dompdf supports the same fonts as the underlying PDF backends: Type 1 (.pfb with the corresponding .afm) and TrueType (.ttf). At the minimum, you should probably have the Microsoft core fonts (now available at: http://corefonts.sourceforge.net/). See below for font installation instructions.
- Untar/unzip the source package in a directory accessible by your webserver.
- Edit dompdf_config.custom.inc.php (in version 0.6) or dompdf_config.custom.inc.php (version 0.5) to fit your installation. If you leave the DOMPDF_PDF_BACKEND setting at 'auto' dompdf will use the bundled R&OS CPDF class.
- Give your webserver write permission on the path specified in DOMPDF_FONT_DIR (lib/fonts by default). Under *nix, ideally you can make the webserver group the owner of this directory and give the directory group write permissions. For example, on Debian systems, Apache runs as the www-data user:
$ chgrp www-data lib/fonts
$ chmod g+w lib/fonts
If your user is not a member of the www-data group or you do not have root privileges, you can make the directory world writable and set the sticky bit:
$ chmod 1777 lib/fonts
Since 0.6 beta 2, dompdf has a configuration/helper page available at www/setup.php. This page will tell you if an extension is missing, and will check if the temp path is writable. It will also tell you what fonts are installed for the CPDF backend (the one used by default).