A connector between WordPress and Picasso IA reads the title or excerpt of a post, generates a cover for it and hands the image back to the draft. You review the picture, write the alt text and keep every cover in one house style before anything goes live.
Every post on a WordPress site wants a featured image, and the last ten you published probably got whichever stock photo was closest to hand. A connector between WordPress and Picasso IA is built to fix that: it reads the title or excerpt, generates a cover for that specific post, and hands the picture back to the draft for you to review before anything goes live. This page explains how that works and where it stops.
A featured image does more work than it looks like. It is the thumbnail in your archive, the card that appears when someone shares the link, and the first thing a reader judges before reading a word. A post without one shows a grey box or a theme placeholder, and a post with a recycled stock photo looks like the five posts around it. Making a custom cover by hand for every article is the kind of task that gets skipped on the busy weeks, which are most of them.
Picasso IA runs 502 models behind one account, 212 of them text-to-image, so a cover can come from an engine that suits the look of your blog. The connector is described as using the same models and the same credit system as the toolkit: every generation costs credits, the amount depends on the model and the settings you pick, and the plans are on the pricing page. Access works with a key you create in your account, and you should treat that key like a password.
One part is available today without any connector: the toolkit runs the same catalog, so you can test your prompt style and your favorite model there right now. If a cover looks right in the toolkit, it is a good candidate for automation. If it does not, no connector will rescue it.
A title is a thin brief. The same sentence can become a photograph, an illustration or an abstract texture, and the right choice depends on what the post is. Decide the approach per post type once, write it down as a style sentence, and let the connector reuse it.
| Post type | Cover approach | What to put in the style sentence | Check before publishing |
|---|---|---|---|
| Tutorial or how-to | Simple object scene that hints at the topic | one clear subject, soft light, plain background, no screens | No fake interface or invented buttons |
| Opinion or essay | Abstract or symbolic still life | muted palette, a single metaphor, generous empty space | The metaphor does not contradict the argument |
| Product or review | Illustration or neutral scene, not a fake photo of the item | flat graphic style, brand colors, no logos | The image does not imply a real product shot |
| News or announcement | Calm graphic cover with a date-neutral look | restrained colors, simple shapes, no people | Nothing suggests a real event that did not happen |
| Roundup or list | Collage-like arrangement of related objects | tidy flat lay, even spacing, consistent palette | Objects match what the list really covers |
Two habits help with any row. First, ask for a plain background with room at the sides, because themes crop featured images differently for the archive, the single post and the social card, and a centered subject survives all three. Second, generate a few variants and read them side by side: a tight spread means the prompt is precise, a wild one means the model is guessing and the style sentence needs another line.
This is the flow the connector is designed around, in plain words. The same five steps work by hand in the toolkit today, which is the fastest way to check that the result is what you want.
Automation should end at the draft, not at the publish button. The connector produces a candidate image, and a person decides whether it goes on the page. That review is quick and catches the problems a model cannot see for itself: a subject that clashes with the tone of the post, an odd object in the corner, a style that drifted from the rest of the blog.
Alt text describes the picture for someone who cannot see it, so write it from what is actually in the image, not from the post title. A model that was given a title does not know what it drew. Look at the cover, then describe it in one plain sentence.
Keep alt text short and literal. If the cover is purely decorative, say so in your theme's settings rather than stuffing keywords into a description. The same rule covers captions: if you add one, it should be true of the image on the page. Reviewing is also where you catch generated text. Image models still garble letters now and then, so a cover with stray lettering in it should be regenerated, not published.
Consistency is what makes a blog look designed rather than assembled. It comes from decisions, not from luck, and the connector can only repeat what you decide. A few choices carry most of the weight:
For other formats that share the same look, the same style sentence carries over to social media posts and poster designs, which keeps a post cover and its promotion visually related.
A connector is good at the repetitive part, turning a title into a decent first image. It is not an art director, and some posts should not get a generated cover at all. Here is where it stops:
Posts about real people or real events are the first case. A generated picture can suggest something that never happened, so use a real photo you have the right to use, or an abstract cover that makes no claim. Product reviews and listings are the second: an invented image of the item misleads readers about what it looks like, so show the real product and keep any generated cover to a neutral graphic.
Readable text and logos are the third. Models are better at lettering than they used to be, but a headline or a brand mark inside the image still needs proofreading, and an exact logo is safer added in a design tool. Thin titles are the fourth: a vague title gives the model nothing to work with and the cover comes out generic, so the excerpt or a one-line description of the picture you want often beats the title alone.
Last is time and credits. Each cover takes a moment to generate and costs credits, so a large backlog of old posts adds up, and models differ in both speed and quality. None of this is a reason to avoid the idea. It is the reason the plan is a draft you review rather than a switch you flip and forget.
That is what the connector is for: it takes the title of a post, combines it with the style sentence you wrote, and asks a text-to-image model for a cover. The picture comes back as a file you review before it becomes the featured image. You can try the same thing in the toolkit today by pasting a title and a style description into any text-to-image model and seeing what you get.
The excerpt usually carries more to draw from, because a title is often a short promise while an excerpt says what the post actually contains. A good test is to generate from both in the toolkit and compare. If the title alone gives you a focused image, keep it simple. If the covers come out generic, switch to the excerpt or add one sentence describing the scene you want.
The approach on this page assumes it does not. The connector produces a cover and returns it to the post, and you decide whether it becomes the featured image. Keeping a review step is the honest design, because a model cannot know whether a picture suits the tone of your article, and a wrong cover on a live post is more work to fix than a right one is to approve.
Yes. The model drew the image from a title, so it has no reliable account of what ended up in the picture. Look at the cover and write one plain sentence describing what is actually visible. That keeps the alt text accurate for people using screen readers and avoids describing an image that is not the one on the page.
Write one style sentence covering palette, lighting and level of detail, and use it on every post, with the same model for your standard cover. Add a reference image when you need a recurring object or mark to look the same. Consistency comes from fixed inputs, so the more you leave to chance per post, the more the covers will drift from one another.
There is no single best, which is why the catalog helps. For text-to-image covers, try flux-2-pro, seedream-4.5 and ideogram-v3-turbo with the same style sentence and keep the one whose look fits your blog. Use nano-banana when you want to edit or restyle an existing image instead of generating from scratch. Run your own test, because taste decides this more than any ranking.
Each generation is paid in credits, and the amount depends on the model and the settings you choose, so a number written here would go out of date. New accounts get free credits, which is enough to test a style. For plan details see the pricing page, and for a sense of what a given model costs, run one generation in the toolkit.
Treat both with care. Short words can come out clean on some models, but longer text still garbles letters often enough that you must proofread every character. An exact logo is safer added afterwards in a design tool or your theme, so the mark stays precisely as it is. If a model does produce text, check it against the title before you publish.
The key is what authorizes requests that spend your credits, so treat it exactly like a password. Create it in your account, paste it only into the connector settings, never into a public post, a shared document or a code repository, and replace it if you think someone else has seen it. Questions about account security go to support.
Yes, and it is the best way to decide whether it suits you. Open the toolkit, pick a text-to-image model, write your style sentence plus a real post title, and generate a few covers. Do that for three or four posts of different types. If the results are good enough to review and approve, automating the same step later is a small change.
Want to see what your next post could look like? Open the toolkit and generate a cover from its title, or ask support how the connectors fit your setup.
Choose your language
