​
How Can I Use Custom Fonts with PDF.co?

If you’re aiming to use a specific font in your PDF output and it’s not among the default options, here’s how you can incorporate custom fonts into your PDF.co workflows.​

​
Supported Methods for Custom Fonts

PDF.co supports the use of custom fonts through the HTML to PDF and HTML Template to PDF APIs. There are two primary methods to include custom fonts:

  1. Google Fonts Integration
    Utilize fonts available onGoogle Fonts . Include them in your HTML using the standard @import or <link> methods.
  2. Embedding Fonts via CSS
    Host your custom font files (e.g., .ttf, .woff) on a server and reference them in your HTML using @font-face in your CSS. For guidance, refer to thisStackOverflow discussion .

Note:_ Due to security and licensing considerations, PDF.co cannot host third-party fonts on its servers._

​
Steps to Implement Custom Fonts

  1. Prepare Your HTML Template
    Incorporate the desired font using one of the methods above.
  2. Use the HTML to PDF API
    Send your HTML content to PDF.co’s HTML to PDF API endpoint.
  3. Verify the Output
    Ensure the generated PDF reflects the custom font as intended.

​
Additional Considerations

  • Font Licensing: Ensure you have the appropriate rights to use and distribute the custom fonts in your documents.​
  • Font Hosting: For optimal performance and reliability, host your custom fonts on a stable and accessible server.

​
Fonts available for PDF Filling and Adding Text to PDF with pdf/edit/add

PDF.co Font List

Arial
Arial Black
Bahnschrift
Calibri
Cambria
Cambria Math
Candara
Comic Sans MS
Consolas
Constantia
Corbel
Courier New
Ebrima
Franklin Gothic Medium
Gabriola
Gadugi
Georgia
HoloLens MDL2 Assets
Impact
Ink Free
Javanese Text
Leelawadee UI
Lucida Console
Lucida Sans Unicode
Malgun Gothic
Marlett
Microsoft Himalaya
Microsoft JhengHei
Microsoft New Tai Lue
Microsoft PhagsPa
Microsoft Sans Serif
Microsoft Tai Le
Microsoft YaHei
Microsoft Yi Baiti
MingLiU-ExtB
Mongolian Baiti
MS Gothic
MV Boli
Myanmar Text
Nirmala UI
Palatino Linotype
Segoe MDL2 Assets
Segoe Print
Segoe Script
Segoe UI
Segoe UI Historic
Segoe UI Emoji
Segoe UI Symbol
SimSun
Sitka
Sylfaen
Symbol
Tahoma
Times New Roman
Trebuchet MS
Verdana
Webdings
Wingdings
Yu Gothic

Japanese Fonts

MS Gothic
MS Mincho
Yu Gothic

Chinese Fonts

SimSun
MingLiU
Microsoft YaHei

Korean Fonts

Malgun Gothic

Hebrew Fonts

Miriam

Arabic Fonts

Aldhabi
Andalus
Arabic Typesetting

​
Where can I find the PDF.co output in Zapier?

The PDF.co output is temporary and expires after an hour by default. The expiration can be extended in the Business plan.

We recommend that you add a third step in your Zap to save the PDF output to a permanent cloud storage such as Google Drive, Dropbox, or similar.

Here’s a step-by-step guide on how to set it up. It starts at Step 6: https://pdf.co/make-pdf-searchable-and-upload-in-google-drive#6.

If you’d like to review the generated output, please check out Step 5 here: https://pdf.co/make-pdf-searchable-and-upload-in-google-drive#5.

​
Who can access the pdf-temp-files, and how long are files stored?

The pdf-temp-files storage is a private Amazon S3 bucket that utilizes strong industry-standard encryption at rest. Uploaded and output files are temporarily stored in this bucket under highly randomized names generated using a secure random generator. Each file is set to expire in 60 minutes by default and is automatically deleted permanently from the bucket upon expiration. Depending on your subscription plan, you may increase the expiration timeout from 5 minutes to 1440 minutes (1,440 minutes = 24 hours) using the expiration parameter. You may also remove a file directly using the file/delete endpoint at any time.

Since the pdf-temp-files storage is a private bucket, files are accessed via a special “signed” link using the Amazon AWS powered signed links mechanism. This mechanism provides an additional layer of security when accessing the file.

The pdf-temp-files bucket is not included in any backups. Only our engineers have temporary access to this bucket, and 2FA is enforced and required for access. Each access session to the storage is automatically logged, and information about the files’ relation to a specific user is stored separately in a different database.

For additional encryption of the file content, you may utilize user-controlled encryption. This feature provides a way to encrypt output file content with your own encryption option using industry-standard AES encryption, which is supported by all platforms, including Salesforce and others.

The output link expires in 1 hour by default. This can be extended up to 24 hours in Business 2 and Business 3 plans. For more information, please visit the Subscription page.

To extend the output link expiration, please add the expiration parameter in your code with value set in minutes. Setting the expiration value to 1440 will generate an output link that expires after 24 hours.

{
    "expiration": 1440
}

On Zapier, please open your PDF.co action setup and look for the Output links expiration field. The default value is 60 minutes. You can change the value up to 1440 minutes.

On Make, please open your PDF.co module and look for the Output links expiration field. The default value is 60 minutes. You can change the value up to 1440 minutes.