Featured Images in WordPress with RenderForm

Creating featured images by hand for every post gets tedious. RenderForm gives you a way to generate them from post content using a template.

This article covers how RenderForm works with WordPress, how the official plugin handles the connection, and how to set it up.

What is RenderForm?

RenderForm is a tool for creating images from templates and passing in data. You build a design in the RenderForm dashboard and mark the parts that should change, such as a post title or category.

Once that is set up, you send values to those dynamic layers through the API. RenderForm generates a new image with that content and returns the finished graphic.

WordPress Integration Overview

RenderForm provides an official WordPress plugin that connects your site to your RenderForm account. The plugin sends post content to the RenderForm API and pulls back a completed image.

When you publish or update a post:

  1. The plugin sends the configured post values to your chosen template.
  2. RenderForm generates an image using those values.
  3. The generated image is added to your Media Library and set as the post’s featured image.

Installing the Plugin

To install the plugin:

  1. Go to Plugins → Add New in your WordPress admin.
  2. Search for RenderForm.
  3. Click Install, then Activate the plugin.

Once installed, go to Settings → RenderForm. You’ll need your API key from your RenderForm dashboard to connect the plugin to your account.

Creating a Template

Templates are created on the RenderForm platform. You can upload your own background image or use their built-in design editor.

When setting up your template, define which elements should be dynamic. For example:

  • A text layer with the variable name title
  • A subheading layer called category

These become the fields the plugin can send values to.

Manually Configuring Field Values

The plugin does not map post fields to template variables automatically. You need to define which values go to which fields.

In the plugin settings, you’ll find a section where you can assign a specific piece of post content to a template field. For example:

  • Assign the post’s title to the title field in your template.
  • Assign the post’s primary category to a category field.

Only the fields you define are sent. If you leave a field blank in the plugin, no data is passed to that layer.

What Happens After Publishing

When a post is published or updated, and the plugin is active, it will:

  • Collect the values you assigned in settings.
  • Send those values to the RenderForm API using your chosen template.
  • Download the resulting image and add it to the Media Library.
  • Assign that image as the post’s featured image.

This runs in the background after each post save or update. The result is a branded, consistent image without manual image editing.

Use Case Example

Say you have a blog and want each post to feature its title over a branded background.

  1. You create a template in RenderForm with a dynamic text field called title.
  2. You configure the plugin to send the post’s title to that field.
  3. Each time you publish, a new image is generated with the title embedded and automatically assigned to the post.

No extra steps needed.

Things to Know

  • The plugin only works on standard posts.
  • All data connections to RenderForm are made securely using your API key.
  • You control exactly what is sent to RenderForm and what is shown in the image.
  • You must create and manage templates in the RenderForm dashboard.

RenderForm removes a repetitive task from the publishing workflow by generating featured images on the fly. It keeps the look of the site consistent and saves time if you publish often.

The plugin setup is straightforward, but you still need to build your own template and decide which post fields to use. Once that is done, it handles image generation in the background.

Tags:

Related posts

Vector | vdev-v0.3.3

Vector vdev v0 3 3: patch release with crash, leak and parsing fixes, connector and tooling improvements, upgrade notes on prechecks, rolling updates, compat

Loki | v3.7.2

Loki v3 7 2: security and CVE fixes, updated S3 client to aws sdk v1 97 3, ruler panic fix for unset validation scheme, S3 Object Lock sends SHA256 checksum

Loki | v3.7.2

Loki v3 7 2: Patch release with CVE fixes, AWS S3 SDK update, ruler panic fix, S3 Object Lock SHA256 checksum support