XeroWP
Titlize
Titlize

Titlize

0/5 (0 ratings) — active installs Updated Aug 2, 2026
featured imageog-imageopen graphseosocial media
Download v1.0.1 Plugin Website
From any featured image, Titlize generates a share-ready Open Graph card automatically.

From any featured image, Titlize generates a share-ready Open Graph card automatically.

Titlize automatically generates Open Graph (OG) images for your WordPress posts and pages. Simply publish your content, and the plugin will create a social media preview image using your featured image and post title.

Key Features

  • Automatic OG Image Generation – Generate OG images automatically when you publish or update posts
  • Per-Post Customization – Override default settings for individual posts with custom titles, subtitles, and styling
  • Preview Before Publishing – See exactly how your OG image will look before you publish
  • Manual Regeneration – Regenerate images anytime with a single click
  • Bulk Regeneration – Update multiple posts at once from the posts list
  • Smart Caching – Avoid unnecessary API calls with intelligent cache invalidation
  • Brand Kit Integration – Use your brand colors and logo from your Titlize account
  • Custom Post Type Support – Enable OG image generation for any post type
  • Gutenberg Block – Insert titled images directly in your post content

How It Works

  1. Configure your API token in Settings > Titlize
  2. Set your default text position, color mode, and other preferences
  3. Publish your posts – OG images are generated automatically
  4. Customize individual posts using the Titlize meta box

Requirements

  • WordPress 6.0 or higher
  • PHP 8.1 or higher
  • A Titlize API account (sign up here) — a free tier generates real Open Graph images (no sandbox); see Terms of Use

Development

The full, unminified source for the block and admin scripts ships inside this plugin under blocks/src/ and admin/src/. The blocks/build/ and admin/dist/ files are compiled from that source with @wordpress/scripts (webpack).

To rebuild from source:

npm install && npm run build:all
  • npm run build — compiles the Gutenberg block (blocks/src blocks/build)
  • npm run admin:build — compiles the admin scripts (admin/src admin/dist)

External services

This plugin relies on the Titlize service to generate Open Graph images. It requires a Titlize account and API token, and it will not generate images without one.

Titlize API — api.titlize.com
What it is: the Titlize image-generation API. What it is used for: turning your featured image and post title into an Open Graph image. When you publish or update a post, preview an image from the meta box, or run a manual/bulk regeneration, the plugin sends to this service: your featured image, the post title and optional subtitle text, and your styling preferences (text position, color mode/hex, font), authenticated with your Titlize API token. The service returns the URL of the generated image.

Titlize image storage — storage.titlize.com and storage.googleapis.com
What it is: where the generated images are hosted (Titlize storage, backed by Google Cloud Storage). What it is used for: after the API returns an image URL, the plugin makes a plain GET request to that URL to download the finished image and save it to your WordPress media library. No personal data is sent other than the request for that specific image.

This service is provided by Titlize. See the Terms of Use and Privacy Policy.

Privacy Policy

Titlize sends data to the Titlize API service to generate images. This includes:

  • Your featured image
  • Post title and subtitle text
  • Styling preferences (position, colors)

No personal user data is transmitted. Generated images are stored in your WordPress media library.

API Token Storage

Your API token is stored obfuscated at rest: it is encrypted with AES-256-CBC keyed on your site’s own WordPress secret key (SECURE_AUTH_KEY, falling back to AUTH_KEY) before being saved to the options table, and the settings screen only ever shows a masked placeholder. This obfuscation-at-rest protects the token against a database-only disclosure (for example a DB dump without wp-config.php); it is not a secrecy guarantee against an attacker who already has both the database and your wp-config.php secret keys. If your site has no WordPress secret keys configured, the plugin refuses to store a token rather than fall back to a built-in default key.

For more information, see the Titlize Privacy Policy.