Vizard Agent

How to make a branded cover image for a social post

Last updated 2026-08-30 · 7 min read

Point Vizard Agent at your website and say what the post is about. Vizard Agent pulls the real colours and logo from the site, digs the background textures out of its code, renders the logo properly, generates any material it needs to match, and composes a cover image in your actual brand.

What is the short version?

A social cover image has to look like it came from the same place as your website. Getting that right means taking the colours and the textures from the site itself rather than from a memory of what they look like.

  1. Go to Vizard Agent and point at your website.
  2. Say what the post is about and what the image should say.
  3. Say what should differ from the last one you made.

What do you need before you start?

Your website and the wording. Vizard Agent takes the palette, the logo and the textures from the site, so no brand guidelines document is needed, and pointing at a previous post gives it the layout to work from.

What do you type into Vizard Agent?

Say what should be different rather than describing the whole thing again. Vizard Agent reads the previous post as the template, so "same layout, different colours because these two blend together" is a complete brief and a far more precise one than a fresh description.

Prompt

Make me a cover image for our post — same layout as the last one but different colours, because those two blend together. Take the colours from [our website]. They should work together without merging. Add some of our marble, and put [the wording] in the middle.

Variants worth knowing:

What does Vizard Agent actually do?

Here is the order Vizard Agent worked in on a real branded cover image. The step worth noticing is the twelfth: it went into the website's code to find the background textures rather than trying to recreate them by eye.

  1. Opens the attached image and checks the client's project history.
  2. Copies the reference screenshot and checks its size.
  3. Checks the colours and the style on the brand's website.
  4. Cuts out the reference post and checks the available tools.
  5. Reviews the reference tile up close to see how it is put together.
  6. Pulls the brand colours and the logo from the site.
  7. Screenshots the site and checks the available typefaces.
  8. Downloads the logo and prepares a preview, then checks the logo rendering tools.
  9. Searches the site's code for its background textures, downloads them, renders the logo, reviews both the dark and the light textures, then generates a marble with gold veining to match and checks the font files.

Step 9's texture hunt is the thing that makes the image belong. A brand's marble or paper background is usually sitting in its stylesheet as an actual file, and using that rather than generating something similar is the difference between matching and resembling.

What does the result look like?

A cover image in the brand's own colours and textures, with the logo rendered at the right weight, the wording set in a matching typeface, and a layout that follows the previous post so the two sit together in a feed without looking like a template with the colours swapped.

Nothing about it is approximated. The colours are the site's values, the texture is the site's file, the logo is the real one rendered rather than a screenshot enlarged.

When does this not work well?

Taking a brand from a website works well when the website genuinely is the brand, and sometimes it simply is not any more. These are the cases where Vizard Agent faithfully reproduces something you would probably rather it had not.

How do you fix a result that came back wrong?

Say what is off about it and why it bothers you. Vizard Agent keeps the sampled colours, all the downloaded textures, the rendered logo and the reference tile, so the palette or the layout can change without re-reading the site.

How does Vizard Agent compare to doing it yourself?

By hand this means eyedropping colours off a screenshot, which gets them nearly right, and recreating a texture that already exists as a file on your own server. Then doing it again next week for the next post.

By hand Vizard Agent
Colours Eyedropped from a screenshot Pulled from the site's own values
Textures Approximated Found in the site's code and downloaded
The logo A screenshot, enlarged Rendered properly
Consistency Drifts post by post Composed against the previous one

Common questions

Do I need brand guidelines? No. Vizard Agent takes the palette, the logo and the textures straight from your website.

Can it match a previous post? Yes. Point at it and Vizard Agent uses it as the layout reference.

What if two brand colours blend together? Say so. Vizard Agent picks a combination from your palette that separates properly.

Will the logo look right? Yes. Vizard Agent renders it rather than enlarging a screenshot of it.

Can it generate a texture? Yes. Vizard Agent matches it to the ones on your site rather than inventing from nothing.

Why take the texture from the code rather than recreating it? Because it is already there as a file. A recreated marble looks like marble; the one on your site looks like your brand.

What shapes can it make? Any shape. Vizard Agent builds square, portrait and story sizes from one composition.

Is the output an image or a video? An image. This is a still deliverable, which is what a post cover needs.

Can it do a whole batch? Yes, and Vizard Agent keeps them consistent more easily when they are made together.

Can it make the matching video too? Yes, from the same sampled brand. Vizard Agent uses the colours, logo and textures it already pulled, so a post cover and a short video end up genuinely matching rather than approximately.

How many posts can share one layout? As many as you like, and that is the point. Vizard Agent composes each against the last, so a feed accumulates into something recognisable rather than a run of separate designs.

Does Vizard Agent check the result? Yes. It reviews the composition against the reference before delivery.