Burnpedia Image Maker – Social Image Designer with 130 Templates

Burnpedia Image Maker is not affiliated with, endorsed by or sponsored by
Pinterest, Inc. Pinterest is their trademark, named here only to say what the
images are for and where the one optional feature posts them.

Every post you publish deserves a Pin, and making one is usually a trip to another
website: export the photo, upload it somewhere, fight a template, download it,
come back. This plugin puts the whole thing inside WordPress.

It is a Pinterest pin designer that lives in your dashboard – a pin maker
that already knows the post you are writing about, so there is no upload step and
no second tab. It is made by Burnpedia.

Open a post and the canvas is already composed — the featured image in place,
the post title as the headline, a sensible template, a 2:3 Pinterest canvas, the
permalink attached. Change what you want and download it. Most Pins take under a
minute.

Do I need an account? No — not to design, download or save to your Media
Library: all of that runs in your browser and on your own site, with no limit,
no watermark and no sign-up. A free account at
burnpedia.app is needed only for two optional things:
posting the finished Pin to Pinterest for you, and AI help that writes a Pin’s
words or makes its background photo (AI help also uses Burnpedia points). Both
are described under External services below.

How Burnpedia Image Maker is different

• It starts from the post, inside WordPress. The canvas opens with the
  post’s featured image, title and permalink in place: nothing to upload, no
  second tab.
• The design work never leaves your site. Templates, editing, downloading
  and saving to the Media Library run in your browser and on this site, and
  send nothing to Burnpedia or anywhere else.
• Made for the Pinterest shape. Every pin template is a real design built
  for a tall 2:3 Pin, not a filter, with a warning when a size is a poor fit.
• The Pin goes back into the post, as its featured image or appended to it,
  from the same screen.

What you get

• 130 templates across two families — text laid over a full-bleed photo, and
  layouts that hold the photo inside a designed frame (magazine cover, side split,
  ticket stub, arch pair, window pane, and many more).
• 40 colour palettes, or your own brand colours.
• Your photos — the post’s featured image, any image already in the post, your
  Media Library, or a file from your computer. Crop with 1–4× zoom and pan.
• Text you can move — drag the headline anywhere on the canvas, resize it,
  restyle it. Seven type choices, colour, size and a legibility scrim.
• Extra elements — up to 12 text blocks, badges and stickers.
• A brand kit — your logo, your colours, your font, saved for this site, so
  every Pin from this blog looks like this blog and every author here gets it.
  Start it in one click from your theme’s own colours, and carry it to the other
  sites you run if you have a Burnpedia account.
• Any size from 400 to 3000 pixels, exported as PNG, JPG or WebP, with a
  warning when a shape is a poor fit for Pinterest.
• A set of Pins for one post – draw up to six at once, each on a different
  template and using a different one of the post’s photos, then send them all
  with one press. They go out one a day.
• Optional AI help – have the Pin title and description written for you, or
  a background photo generated from a sentence. The price in Burnpedia points and
  your balance are shown before you press, a failed attempt costs nothing, and
  the photo is saved to your Media Library. An administrator can also let
  editors and authors use it, with a daily limit per person.
• Seasonal and niche template packs – holiday packs appear about two months
  before the day (Halloween, Thanksgiving, Christmas, New Year, Valentine’s Day,
  Easter, summer, back to school), alongside packs for recipes, product
  roundups and quotes.
• Pins for your older posts – a list of every published post that has no
  Pin yet, with a Design a Pin button on each. Tick the ones you want and they
  go out one a day, never on a day that is already full.
• A Pin drafted when you publish – with a brand kit saved, every new post
  gets a Pin drawn in your brand and template, waiting in the editor for you to
  approve, edit or discard. Nothing is posted until you press approve.
• How your Pins did – views, saves, close-ups and visits to your site for
  the Pins sent from this site, and which of your templates people save most.
  New Pins start with small numbers, and the screen says so.
• Undo and redo, and an autosaved draft so a closed tab does not lose work.

What you can do with a finished Pin

• Download it — full resolution, no watermark, ever.
• Save it to your Media Library.
• Set it as the post’s featured image.
• Insert it into the post (it asks first, and it only ever appends).
• Send it to Pinterest — optional, and the only part that needs an account.

Nothing is locked

There is no pro version of the editor, no watermark and no trial, and nothing in
the editor stops working without an account. Two optional extras are services
Burnpedia runs, and they are the only things that can cost anything: posting to
Pinterest, which is metered by how many Pins a day you post, and AI help, which
uses Burnpedia points and shows the price before you press. Everything else here
is simply free.

External services

This plugin is a client for Burnpedia (https://burnpedia.app), a Pinterest
scheduling service we operate. It is used for two optional features: sending a
finished Pin to Pinterest, and AI help in the editor.

Nothing is sent until you take one of the steps below. With no API key saved, a
request leaves this site only in these four cases, each described below: you
press Connect this site, you switch on the optional install count, you press
Send report on the Report a bug screen, or you open the More plugins
screen (which asks WordPress.org, not Burnpedia). Nothing happens on activation.
There is no third-party asset — every script,
style and font in this plugin is served from your own site.

No request to Burnpedia carries your site’s address in its headers: each
one sets its own User-Agent (WordPress’s default one names the site). The More
plugins list is not one of them: WordPress fetches it itself, through
plugins_api() as Plugins → Add New does, with that default User-Agent.
Where a request does send the site’s address, a permalink or an image address,
the list below says so.

Pressing Connect this site makes exactly one kind of request, and it carries
nothing about you or your site:

• POST https://burnpedia.app/api/site-connect/claim — after you press
  Connect this site, while you are approving the connection on burnpedia.app.
  Sends: two random strings this site generated for that one connection, and the
  plugin’s name and version. Receives: a short status word – whether you have
  approved it yet – and, once you have, your new API key, which the plugin saves
  for you. Nothing else comes back. Your site’s address and name are shown on the
  approval page because they travel in the link your browser opens; this request
  does not carry them, not even in its User-Agent header. If you approve nothing,
  no key is ever created and the request stops on its own after fifteen minutes.

When a key is saved, these requests are made, and only these:

• GET https://burnpedia.app/api/v1/me — when an administrator opens the Send
  panel or the Connection screen, and when a key is saved; and, only if an
  administrator has switched on AI help for the team, when an editor or author
  opens the AI panel (so the price is shown before they press anything). Sends:
  your API key. Receives: your plan, how many Pins you have posted today, your
  AI points balance and prices, and whether a Pinterest account is connected.
• GET https://burnpedia.app/api/v1/boards — when an administrator opens the
  Send panel, to list your Pinterest boards. Sends: your API key. Receives: board
  names and ids.

• POST https://burnpedia.app/api/v1/pins — only when you press Send to
  Pinterest. Sends: your API key, the public URL of the Pin image you just
  saved to your Media Library, the Pin title, the post’s permalink, and the board
  you chose (or a board name taken from the post title). Pinterest then downloads
  the image from your site at that URL.

• GET https://burnpedia.app/api/v1/analytics/site — only when an administrator
  opens How your Pins did in the editor, at most once every fifteen minutes.
  Sends: your API key and this site’s address. Receives: the impressions, saves
  and clicks Burnpedia has already recorded for Pins that link to this site. It
  does not ask Pinterest anything.

• GET https://burnpedia.app/api/v1/brand-kit — only when an administrator
  presses Use my account’s kit here in the Brand kit panel. Sends: your API
  key. Receives: the colours, font and logo address saved on your Burnpedia
  account, so the same brand can be used on more than one site.

• PUT https://burnpedia.app/api/v1/brand-kit — only when an administrator
  presses Save to my Burnpedia account. Sends: your API key and this site’s
  brand kit – three colour values, a font name, and your logo’s address.

• POST https://burnpedia.app/api/v1/copy — only when someone presses Write it
  for me in the optional AI panel: an administrator, or an editor or author if
  an administrator has switched on AI help for the team. Sends: your API key, the
  Pin title you have typed, and the post’s permalink. Receives: a suggested
  title, description and keywords, and how much AI credit that used.

• POST https://burnpedia.app/api/v1/images — only when someone presses
  Generate the photo in the optional AI panel: an administrator, or an editor
  or author if AI help is switched on for the team. Sends: your API key, the
  description of the photo you typed, and the shape you chose. Receives: the
  address of the generated
  image, and how much AI credit that used.
• GET https://burnpedia.app/api/uploads/... — immediately after the request
  above, to download that image so it can be saved into your own Media Library.
  Sends: nothing but the request for that address (no API key). Receives: the
  image file. Only an address that burnpedia.app itself just returned is ever
  fetched.

The AI panel is optional and appears only when a key is saved. Designing,
editing, downloading and saving a Pin to your Media Library send nothing off
this site (the editor calls only this site’s own REST API for them); they work
with no account, and nothing in this plugin charges for them.

Your brand kit is stored on this site and works with no account at all. Those
two requests happen only when you press one of those two buttons, and never on
their own.

Every request to Burnpedia also carries the plugin’s name and version.

Burnpedia’s terms: https://burnpedia.app/terms
Burnpedia’s privacy policy: https://burnpedia.app/privacy

Pinterest itself is never contacted by this plugin. You connect Pinterest once,
on Burnpedia, through Pinterest’s own login screen; this plugin never sees or
stores a Pinterest credential.

Burnpedia is our own service and is not affiliated with Pinterest, Inc.

The install count (optional, off by default). WordPress.org does not tell
plugin authors how many sites are running their plugin — for this plugin it
publishes no figure at all. If you switch this on under Image Maker → Connection, this site
sends a short report:

• POST https://burnpedia.app/api/plugin-insights — once when you switch it on,
  then at most once a week while an administrator is using wp-admin, once if you
  deactivate the plugin, and once if you delete it. Sends exactly nine things: a
  random ID generated on this site, which plugin and which version, which of
  those four events it is, your WordPress version, your PHP version, your site
  language, whether this is a multisite network, and whether an API key is saved
  (true or false — never the key). Receives: nothing your site uses.

No install-count report carries your website address, not even in the
User-Agent header: the plugin sends its own. The random ID is made up on your
server and means nothing outside it. Answering “No, send nothing” sends nothing
at all. Switch the setting off and the ID is deleted, so counting
stops and a later change of mind cannot be joined to it. It is off until you
choose it, no feature depends on it, and nothing about any reader or any
logged-in user is in it.

Report a bug (only when you send one). The Image Maker → Report a bug screen
sends what you type straight to the people who build this plugin. Nothing is sent
until you press Send report, and the screen lists what goes with it first:

• POST https://burnpedia.app/api/plugin-bug-report — sends your description,
  the email address you leave for a reply (optional — leave it empty and we
  cannot answer), this plugin’s name and version, your WordPress version, PHP
  version, theme name and version, site language, whether this is a multisite
  network, and whether an API key is saved (true or false — never the key).
  Your site’s address is sent only if you leave “Include this site’s address”
  ticked (it starts ticked; untick it and the address is not sent, not even in
  the request’s headers). Receives: a reference number for your report. We use a report only
  to answer you and to fix the problem. No API key or account is needed.

More plugins (only when you open it). The Image Maker → More plugins screen
lists our other free plugins. When an administrator opens it, WordPress asks
WordPress.org (https://api.wordpress.org/plugins/info/) for that list through
its own plugins_api() — the same request WordPress makes on Plugins → Add
New — and keeps the answer for twelve hours. Installing one uses WordPress’s
own installer and downloads it from WordPress.org. Nothing is installed or
activated unless you press its button, and nothing is sent to Burnpedia.