Install wkhtmltopdf on linux

Wkhtmltopdf – A Smart Tool to Convert Website HTML Page to PDF in Linux

Wkhtmltopdf is an open source simple and much effective command-line shell utility that enables user to convert any given HTML (Web Page) to PDF document or an image (jpg, png, etc).

Wkhtmltopdf is written in C++ programming language and distributed under GNU/GPL (General Public License). It uses WebKit rendering layout engine to convert HTML pages to PDF document without loosing the quality of the pages. Its is really very useful and trustworthy solution for creating and storing snapshots of web pages in real-time.

Wkhtmltopdf Features

1. Open source and cross platform.
2. Convert any HTML web pages to PDF files using WebKit engine.
3. Options to add headers and footers
4. Table of Content (TOC) generation option.
5. Provides batch mode conversions.
6. Support for PHP or Python via bindings to libwkhtmltox.

In this article we will show you how to install Wkhtmltopdf program under Linux systems using source tarball files.

Install Evince (PDF Viewer)

Let’s install evince (a PDF reader) program for viewing PDF files in Linux systems.

Download Wkhtmltopdf Source File

Download wkhtmltopdf source files for your Linux architecture using Wget command, or you can also download latest versions (current stable series is 0.12.4) at wkhtmltopdf download page.

On 64-bit Linux OS

On 32-bit Linux OS

Install Wkhtmltopdf in Linux

Extract the files to a current working directory using following tar command.

Install the wkhtmltopdf under /usr/bin directory for easy execution of program from any path.

How to Use Wkhtmltopdf?

Here we will see how to covert remote HTML pages to PDF files, verify information, view created files using evince program from the GNOME Desktop.

Convert Website HTML Page to PDF File

To convert any website HTML web page to PDF, run the following example command. It will convert the given webpage to 10-Sudo-Configurations.pdf in current working directory.

Sample Output :

View Generated PDF File

To verify that the file is created, use the following command.

Sample Output :

View Information of Generated PDF File

To view the information of generated file, issue the following command.

Sample Output :

View Created PDF File

Take a look at the newly created PDF file using evince program from the desktop.

Sample Screenshot :

Looks pretty nice under my Linux Mint 17 box.

View Website Page in PDF

Create TOC (Table Of Content) of a Page to PDF

To create a table of content for a PDF file, use the option as toc.

Sample Output :

To check the TOC for the created file, again use evince program.

Sample Screenshot :

Take a look at the picture below. it looks even more better than the above.

Create Website Page to Table of Contents in PDF

Wkhtmltopdf Options and Usage

For Wkhtmltopdf more usage and options, use the following help command. It will display list of all available options that you can use with it.

If You Appreciate What We Do Here On TecMint, You Should Consider:

TecMint is the fastest growing and most trusted community site for any kind of Linux Articles, Guides and Books on the web. Millions of people visit TecMint! to search or browse the thousands of published articles available FREELY to all.

If you like what you are reading, please consider buying us a coffee ( or 2 ) as a token of appreciation.

We are thankful for your never ending support.

Источник

Установка wkhtmltopdf & wkhtmltoimage в Ubuntu 20.04 | 18.04 / Debian 10 | 9

Установка wkhtmltopdf & wkhtmltoimage в Ubuntu 20.04 | 18.04 / Debian 10 | 9

В этом руководстве мы установим wkhtmltopdf и wkhtmltoimage в системе Ubuntu / Debian Linux. wkhtmltopdf и wkhtmltoimage — это инструменты командной строки с открытым исходным кодом (LGPLv3), используемые для рендеринга HTML в PDF и различные форматы изображений с помощью механизма рендеринга Qt WebKit.

Версии этих инструментов, доступные в системе Ubuntu / Debian Linux, старые. Чтобы установить последнюю версию wkhtmltopdf и wkhtmltoimage в Debian 10 / Ubuntu 20.04 / 18.04 Linux, вам необходимо вручную загрузить и установить из пакета .deb . Эти инструменты работают полностью « без головы » и не требуют отображения или службы отображения.

Установка wkhtmltopdf в Ubuntu 20.04 | 18.04 и Debian 10 | 9

Загрузите последний предварительно скомпилированный двоичный файл со страницы выпусков . Последний выпуск на момент обновления этой статьи — 0.12.6.

Установка wkhtmltopdf в Ubuntu 20.04 / 18.04

Результат успешной установки выглядит следующим образом.

Установка wkhtmltopdf в Debian 10 / Debian 9

Установите инструмент командной строки wget.

Установите wkhtmltopdf & wkhtmltoimage в Debian 10/9 Linux

Проверьте версию wkhtmltopdf и wkhtmltoimage, чтобы убедиться, что установка прошла успешно.

Использование wkhtmltopdf в Ubuntu / Debian

Например, если вы хотите преобразовать веб-страницу в PDF, используйте синтаксис команды:

Будет создан файл pdf, и вы можете открыть и просмотреть его содержимое.

Аналогичный синтаксис применяется при преобразовании в изображение.

Ознакомьтесь с руководствами, в которых используется инструментарий wkhtmltopdf.

Источник

All downloads are currently hosted via GitHub releases, so you can browse for a specific download or use the links below.

Do not use wkhtmltopdf with any untrusted HTML – be sure to sanitize any user-supplied HTML/JS, otherwise it can lead to complete takeover of the server it is running on! Please read the project status for the gory details.

Stable

The current stable series is 0.12.6, which was released on June 11, 2020 – see changes since 0.12.5.

OS/Distribution	Supported on	Architectures
Windows	Installer (Vista or later)	64-bit	32-bit
	7z Archive (XP/2003 or later)	64-bit	32-bit
macOS	Installer (10.7 or later)	64-bit
Debian	10 ( buster )	amd64	i386	arm64	ppc64le	raspberrypi
	9 ( stretch )	amd64	i386	arm64	raspberrypi
Ubuntu	20.04 ( focal )	amd64	arm64	ppc64le
	18.04 ( bionic )	amd64	i386	arm64	ppc64le
	16.04 ( xenial )	amd64	i386	arm64
CentOS	8	x86_64	aarch64	ppc64le
	7	x86_64	i686	aarch64	ppc64le
	6	x86_64	i686
Amazon Linux	2	x86_64	aarch64	lambda zip
openSUSE Leap	15	x86_64	aarch64	ppc64le
Arch Linux	20200705	x86_64

All of the above packages were produced automatically via Azure Pipelines and were built on the latest OS/distribution patch release at the time of the release.

Archive

Please note that bug reports will not be accepted against the following, which are considered obsolete. It is recommended to use the latest stable release instead, and report an issue if there is a regression from a previous release.

Date	Release
2018-06-11	0.12.5
2019-04-30	0.12.1.4 (linux-only)
2016-11-22	0.12.4
2016-03-02	0.12.3.2 (windows-only)
2016-01-30	0.12.3.1 (windows-only)
2016-01-20	0.12.3
2015-07-12	0.12.2.4 (windows-only)
2015-06-20	0.12.2.3 (windows-only)
2015-04-06	0.12.2.2 (windows-only)
2015-01-19	0.12.2.1
2015-01-09	0.12.2
2014-06-26	0.12.1
2014-02-06	0.12.0

If you need versions older than 0.12.0 , you can look at the obsolete downloads.

Why do you have static builds with patched Qt?

Good question. Some features require you to use a patched Qt, because those aren’t yet upstream – please read the project status for a longer explanation.

Most Linux distributions (quite understandably) would prefer that this project upstreamed the patches, and choose to compile without those features. This leads to quite different behavior – you get a later web engine, but behavior can vary from distribution to distribution.

Why are there no “generic” Linux builds (which were provided earlier)?

Although the builds are static, it is very important to understand what it means in the context of Qt – on which wkhtmltopdf is built. A static build means that only Qt is linked in this manner – the remaining system packages still need to be installed. Over a period of time, major areas of divergence between distributions were found by trial and error:

• different library versions: not every distribution provides the same versions. This was especially the case for libpng and libjpeg , with a lot of distributions choosing between the 1.2, 1.5 and 1.6 series for the former and multiple versions of libjpeg and/or its fork libjpeg-turbo . While this could be addressed easily by linking them statically (and was actually done so for previous releases) – it broke down when it came to the next point.
• different OpenSSL versions: due to OpenSSL having a bad track record then (it’s better now), distributions started aggressively upgrading their OpenSSL version and disabling unused parts of the library. This led to a situation where there was effectively zero backward compatibility and things started breaking randomly – see #3001 for a very long read of the problems faced. This was the direct motivation to create a separate packaging repository.
• incompatible libc: not every distribution has the same glibc version. If you compile with a later version, it won’t work on a distribution which uses an older version. This was worked around earlier by using CentOS 6 (which had an old enough glibc version). But due to the rise of Docker, the alpine image became very popular. This doesn’t use glibc at all, but the musl libc. So the generic binaries never really worked on Alpine.

While Python has also tried to do this using manylinux – it doesn’t always work well (e.g. alpine is not recommended with binary wheels if you google for it), and requires you to statically link everything. This may work for them, but wkhtmltopdf also depends on the runtime configuration on actual fonts installed (i.e. fontconfig and freetype2 ). It’s not possible to abstract everything out and test/fix everything for every OS/distribution with the limited resources this project has – it makes more sense to make distribution-specific versions which are almost guaranteed to work, as they use the specific versions that the distribution has packaged.

I don’t see an appropriate download for my platform!

If the distribution you are using is listed:

• but not the specific patch release – try it, as it’s very likely to work regardless.
• the major release isn’t listed – we only support LTS versions, so try a LTS version older than your release.
• cannot install package – you can always extract it (google for extract from ), but you’ll need to have the dependencies installed.

Head over to the packaging repository and start a discussion if your platform isn’t listed.

How do I use it with FaaS setups?

You’ll need to extract the distribution-specific package, bundle it with necessary libraries, configuration and/or fonts and then upload it. See this StackOverflow question for Google Cloud Functions. PRs are welcome to expand this section, if you have more information about this – this is not a setup that the maintainer uses 😄

How do I use it in AWS Lambda?

All files required for lambda layer are packed in one zip archive (Amazon Linux 2 / lambda zip). You may test it locally by unpacking the archive into the layer directory and running next commands:

After that, you may find a pdf file generated from the google home page in your layer directory.

To use wkhtmltox in your lambda function you may put the content of the archive together with your lambda function or create a layer. Don’t forget to provide an environment variable for fontconfig ( FONTCONFIG_PATH=/opt/fonts ).

In case you use Serverless framework you may add the next lines to your serverless.yml file:

Symantec reports a virus WS.Reputation.1 for the Windows builds

This is a false positive reported because Symantec has not seen this file before – see this clarification for details.

Источник