PDFCrowd Blog

Product updates, tips & tricks

We have released a new version of our WebSave product.

Version 1.3.0

New Features

  • window.WebSave.initButton(element) - Manually initialize buttons added to the page after WebSave loads. Required for single-page applications and dynamically generated content.
    Example:
    window.WebSave.initButton(document.querySelector('.my-button'))

Users often need to export web pages as PDFs. The browser's window.print() function produces inconsistent results: CSS backgrounds are omitted, page breaks occur mid-element, and layout rendering differs from the screen display.

WebSave as PDF provides a client-side solution for adding PDF export to web applications. It captures the current page state directly in the browser. This guide covers integration for React, Preact, Vue, Angular, Svelte, Astro, and SolidJS.

This guide helps you migrate from the Save to PDF Link service to WebSave as PDF. The migration is straightforward and can be completed in a few simple steps.

Why migrate? Save to PDF Link is a legacy service that relies on the HTTP referrer header, which is increasingly unreliable due to browser privacy features and HTTPS policies. WebSave as PDF works more reliably and offers better customization options.

We have released version 4.5.0 of our WordPress Plugins and 6.5.0 of our API client libraries.

New:

  • The error handling system has been updated. This includes revised status codes and messages, as well as the addition of new methods to the error class: getStatusCode(), getReasonCode(), and getDocumentationLink(). The getCode() method is deprecated and should be replaced with getStatusCode().