# Journal and migration guides

[All Marqius knowledge](../index.md)

- [Journal for print production teams | Marqius](blog.md) — Practical guides to PDF generation and print production, from replacing wkhtmltopdf to testing templates and clearing a press proof.
- [Install Marqius wkhtmltopdf with APT on Debian | Marqius](blog-install-marqius-with-apt.md) — Install Marqius with APT on Debian 12 or 13. Keep your old wkhtmltopdf command while you check a PDF with Marqius.
- [Install wkhtmltopdf on Debian 12 or 13: Bookworm and Trixie | Marqius](blog-install-wkhtmltopdf-debian.md) — Bookworm still has wkhtmltopdf. Trixie removed it. Find out why your install stopped and how Marqius can keep your PDF app working.
- [Measure the speed of a PDF batch | Marqius](blog-measure-pdf-batch-speed.md) — Measure preparation, rendering and review separately to see what is holding up a print run.
- [Migrate CakePdf off wkhtmltopdf | Marqius](blog-migrate-cakepdf-off-wkhtmltopdf.md) — Keep your CakePdf view and engine. Change the program that turns the view into a PDF.
- [Switch django-wkhtmltopdf to the Marqius executable | Marqius](blog-migrate-django-wkhtmltopdf.md) — Keep your Django view and template. Change one setting and test the same download.
- [Migrate Elixir pdf_generator off wkhtmltopdf | Marqius](blog-migrate-elixir-pdf-generator.md) — Keep your Elixir PDF call. Set the Marqius path in the release’s runtime settings.
- [Switch go-wkhtmltopdf to the Marqius executable | Marqius](blog-migrate-go-wkhtmltopdf.md) — Point the Go library at Marqius at startup. Keep the pages and options you already use.
- [Switch Java wkhtmltopdf wrapper to the Marqius executable | Marqius](blog-migrate-java-wkhtmltopdf-wrapper.md) — Keep your Java PDF calls. Pass the Marqius path when you create the PDF object.
- [Migrate Laravel Snappy off wkhtmltopdf | Marqius](blog-migrate-laravel-snappy-off-wkhtmltopdf.md) — Keep your Blade template and invoice job. Update the PDF program used by Laravel Snappy.
- [Switch Node.js wkhtmltopdf to the Marqius executable | Marqius](blog-migrate-node-wkhtmltopdf.md) — Keep the Node wkhtmltopdf library and its stream. Set the command to Marqius.
- [Switch phpwkhtmltopdf to the Marqius executable | Marqius](blog-migrate-phpwkhtmltopdf.md) — Keep the same PHP calls. Set the binary option to Marqius and check the file.
- [Migrate Python pdfkit off wkhtmltopdf | Marqius](blog-migrate-python-pdfkit-off-wkhtmltopdf.md) — Keep Python pdfkit. Change the PDF program it starts and check one invoice.
- [Migrate Rotativa.AspNetCore off wkhtmltopdf | Marqius](blog-migrate-rotativa-off-wkhtmltopdf.md) — Keep ViewAsPdf and your existing view. Put Marqius in the folder where Rotativa looks.
- [Migrate Ruby PDFKit off wkhtmltopdf | Marqius](blog-migrate-ruby-pdfkit-off-wkhtmltopdf.md) — Keep the Ruby PDFKit gem. Give it the Marqius path and check one statement.
- [Migrate KnpLabs Snappy off wkhtmltopdf | Marqius](blog-migrate-snappy-off-wkhtmltopdf.md) — Keep KnpLabs Snappy and your PHP invoice code. Give Snappy a new PDF program.
- [Migrate Symfony KnpSnappyBundle off wkhtmltopdf | Marqius](blog-migrate-symfony-knp-snappy-bundle.md) — Keep your Symfony PDF service. Point its Snappy setting at Marqius.
- [Migrate Rails wicked_pdf off wkhtmltopdf | Marqius](blog-migrate-wicked-pdf-off-wkhtmltopdf.md) — Keep your Rails views and wicked_pdf. Change the executable path and test the same report.
- [Test the record that breaks the page | Marqius](blog-test-the-record-that-breaks-the-page.md) — Proof a typical record alongside long addresses, missing fields and tables that span pages.
- [What to send your printer before a repeat run | Marqius](blog-what-to-send-your-printer.md) — Agree on trim, bleed and the file the printer expects before you build the full batch.
- [wkhtmltopdf is unmaintained: Your options in 2026 | Marqius](blog-wkhtmltopdf-deprecated-alternatives.md) — wkhtmltopdf is archived. Try Marqius as a drop-in replacement, compare Chromium, Gotenberg and WeasyPrint, and check your own PDF before switching.
- [wkhtmltopdf vs Gotenberg: When a PDF API makes sense | Marqius](blog-wkhtmltopdf-vs-gotenberg.md) — Try Marqius to keep your PDF call. Consider Gotenberg if several apps need a shared service for invoices, Word files or spreadsheets.
- [wkhtmltopdf vs headless Chromium: What changes when you switch | Marqius](blog-wkhtmltopdf-vs-headless-chromium.md) — Try Marqius to keep your current PDF code. Use Chromium when your report needs a browser to load its data or draw its charts.
