PFont

PFont keeps one central font library and adds those fonts to the native font dropdowns of the editors and builders you already use. It only uses documented, verified hooks and never edits core, theme or builder files.

What it does

• Upload WOFF2, WOFF, TTF and OTF files. Every file is checked by its real contents (magic bytes), not only by its name.

• Add Google Fonts from the CDN (Google or the privacy-friendlier Bunny Fonts), or download them to your own server with one click.

• Ships five Persian/Arabic presets you can add in one click: Vazirmatn, Estedad, Parastoo, Lalezar and Markazi Text (all SIL Open Font License). Nothing is enabled automatically.

• Loads a font only on pages that actually use it. Pages without custom fonts get no extra CSS, requests or JavaScript.

• WOFF2 first, font-display: swap by default, preconnect only when a CDN font is used.

• Honest integration status screen: every integration shows Active, Limited, Unsupported or Not detected, with the reason.

• A searchable library that previews every font in your own text, in Persian or Latin, at any size.

• A type tester for each font: weight, italic, size, line height, alignment and right-to-left, plus a size waterfall, the character set and copyable CSS.

• Optional: use one of your fonts for the WordPress admin area (Settings → WordPress admin). Icons, code fields and the content you edit keep their own fonts.

Integrations

• Classic Editor (TinyMCE): font dropdown, fonts preview inside the editor.

• Block Editor: fonts appear in Typography → Font for every block and in Global Styles. Theme fonts are kept (the list is appended, not replaced).

• Elementor: own “PFont” group in every typography control. Elementor’s own Google entries are never overwritten by CDN copies.

• Astra: fonts appear in the Customizer typography controls. Local fonts are never sent to Google.

• Kadence: fonts appear in the Customizer. GeneratePress: type the family name in its Font Manager; the plugin loads the files.

Themes without a public font hook are reported as unsupported instead of being hacked.

Divi and WoodMart are not integrated: both already include their own custom font upload, so add the font there (Divi: the Upload button inside any font menu; WoodMart: Theme Settings → Typography → Custom fonts).

Privacy

Fonts loaded from a CDN send visitors’ IP addresses to that CDN. A German court (LG München I, 20 January 2022, 3 O 17493/20) awarded damages for embedding Google Fonts without consent. Use “Host on this server” (or uploaded files) to avoid third-party requests.

This is not legal advice.

External services

This plugin can connect to one of two font services. Which one is used depends on Settings → Font CDN (Google Fonts by default). Uploaded fonts and fonts hosted on your server use no external service.

com), provided by Google.

• When: on pages that use a font you added from Google and did not host locally; in the editors, so the font can be previewed; on the plugin’s Library screen, to preview the Persian and Arabic presets; when you save such a font (to check the name and weights); and once when you choose “Host on this server” (to download the files).

• What is sent: the font family name, the weights and styles requested, and, as with any web request, the IP address and user agent of the browser or server making it. No account, form or content data is sent.

• Google Fonts privacy FAQ: https://developers.google.com/fonts/faq/privacy

• Terms: https://policies.google.com/terms

• Privacy policy: https://policies.google.com/privacy

o. Used instead of Google Fonts, in the same situations and with the same data, when you select it under Settings → Font CDN.

• About: https://fonts.bunny.net/about

• Terms: https://bunny.net/tos/

• Privacy policy: https://bunny.net/privacy/