HTML to PDF with Google Apps Script and Cloud Functions

Introduction

In today’s digital workflows, turning web‑based content into portable, print‑ready documents is a common need. Whether you are generating invoices, reports, or marketing brochures, a PDF version guarantees consistent formatting across devices and platforms. Google Workspace offers a powerful, scriptable environment that can automate this conversion directly inside your Drive, eliminating the need for third‑party software. By leveraging Google Apps Script together with Cloud Functions, you can take any HTML file—whether stored as a Google Doc, a static web page, or a dynamic template—and produce a high‑quality PDF with just a few lines of code. This article walks you through the entire process, from setting up the script editor to deploying a scalable cloud‑based solution, so you can streamline document generation in your organization.

Setting Up the Google Apps Script Environment

Begin by opening a new Google Apps Script project from Google Drive (New ▶ More ▶ Google Apps Script). Give the project a clear name, such as HTML‑to‑PDF Converter. In the script editor, you’ll need to enable the Drive and HtmlService services, which are available by default. Create a simple function that fetches an HTML file stored in Drive:

• function getHtmlFile(fileId) – uses DriveApp.getFileById(fileId).getBlob().getDataAsString() to retrieve the raw HTML.
• Validate that the file’s MIME type is text/html to avoid processing non‑HTML content.

Once this groundwork is in place, you have a reliable way to pull any HTML source into your script, setting the stage for conversion.

Creating a Function to Render HTML as PDF

The core conversion relies on HtmlService. Pass the HTML string to HtmlService.createHtmlOutput(html), then call .getAs('application/pdf') to obtain a PDF blob. A robust implementation looks like this:

• function htmlToPdf(html) – creates an HtmlOutput with a defined setWidth and setHeight to control page dimensions.
• Apply .setSandboxMode(HtmlService.SandboxMode.IFRAME) for better rendering of external resources.
• Return the PDF blob, which can be saved directly to Drive or sent via email.

Because the rendering engine runs on Google’s servers, most CSS, inline styles, and simple JavaScript are respected, producing a faithful PDF replica of the original HTML.

Storing and Managing PDFs in Google Drive

After conversion, the PDF blob should be persisted in a logical folder structure. Use DriveApp.createFolder('Converted PDFs') or locate an existing folder by name or ID. Then:

• folder.createFile(pdfBlob).setName(‘Report_’ + new Date().toISOString() + ‘.pdf’) – ensures each file has a unique, timestamped name.
• Set appropriate sharing permissions with .setSharing(DriveApp.Access.PRIVATE, DriveApp.Permission.VIEW) or share with a team group as needed.
• Optionally, write metadata (e.g., source HTML ID, conversion date) using the file’s .setDescription() method for easier future retrieval.

Organizing PDFs this way not only keeps Drive tidy but also enables downstream automation, such as batch downloads or archival processes.

Automating the Process with Cloud Functions

For high‑volume or event‑driven scenarios, move the conversion logic to a Google Cloud Function. Deploy the Apps Script code as a callable HTTP endpoint, then trigger it from Cloud Functions using the googleapis client library. Typical steps include:

• Export the Apps Script project as a web app with doPost(e) handling JSON payloads containing fileId.
• Create a Cloud Function (Node.js or Python) that receives a Pub/Sub message or HTTP request, forwards the fileId to the Apps Script endpoint, and returns the PDF URL.
• Set up Cloud Scheduler or Cloud Pub/Sub to invoke the function on a regular basis, enabling automated report generation without manual intervention.

This architecture decouples the conversion workload from user‑initiated scripts, providing scalability, logging, and error‑handling capabilities native to Google Cloud.

Conclusion

Converting HTML to PDF within the Google ecosystem no longer requires external tools or complex server setups. By harnessing Google Apps Script’s HtmlService and coupling it with Drive’s storage API, you can create a lightweight, reliable converter that runs entirely in the cloud. Adding a Cloud Function layer transforms the solution into a scalable service that reacts to events, schedules, or API calls, making it ideal for enterprises that need automated document generation at scale. Follow the steps outlined—from environment setup and HTML retrieval, through rendering and storage, to cloud‑based automation—and you’ll have a fully functional pipeline that turns any web‑based content into polished PDFs, ready for distribution, archiving, or compliance purposes.