Decide What the Image Must Explain
Use generated images for illustration. Use real sources and exact chart tools when the visual needs to establish a fact.
Start with the visual's job. A conceptual illustration can introduce a topic, a diagram can explain a workflow, and a screenshot can show an actual interface. These are different requirements. Image generation is a reasonable choice for an original illustration, but it is unsuitable for fabricating a genuine interface state or documented result.
Ask what the reader should understand after seeing the image. If the answer is only that the page looks less empty, consider whether the asset is necessary. A table or simple labeled process diagram may communicate the topic more clearly than a decorative photograph.
Use exact data tools for numerical charts. Generated bars, ratings, or statistics that look plausible are not acceptable evidence. Keep the factual content of the visual as carefully checked as the accompanying prose.
Write a Specific Visual Brief
Describe the subject, purpose, composition, style, and intended placement. A useful brief might ask for an editorial illustration of research notes becoming an article, with a restrained palette and clear space for a heading. It should not ask for fake logos, invented user reviews, or a screenshot of an unobserved feature.
Keep instructions focused on details that matter. Specify what should be omitted, especially text, misleading interface elements, or unnecessary objects. If you need precise labels, add them as real HTML or vector text after creating the illustration rather than relying on rendered text inside the image.
For a consistent publication, prepare a short visual style guide. Reuse the palette, composition preferences, and illustration approach while allowing each image to reflect its own topic.
Choose Model, Style, and Dimensions
The KoalaImages creation guide describes prompt entry, model, style, image size, generation count, reference images, and prompt enhancement. Select those settings to suit the asset's placement and available credit budget.
A wide hero illustration and a square related-reading thumbnail have different cropping needs. Choose dimensions before generating, and allow space around the main subject so the visual remains understandable on smaller screens.
Compare model options with one representative brief if visual quality matters to your publication. Higher cost should be justified by a result you can actually see and use. Check current credit rates in the interface instead of projecting them from an old model list.
| Visual Type | Appropriate Use | Required Check |
|---|---|---|
| Generated illustration | Concept and visual identity | Meaning and misleading details |
| Real screenshot | Actual interface evidence | Source and current version |
| Data chart | Verified numerical comparison | Units, scale, source, and table equivalent |
| Process diagram | Explain steps or decisions | Accurate sequence and text alternative |
- 01Define the visual purpose
- 02Write the brief
- 03Choose format and style
- 04Inspect the result
- 05Prepare the web asset
Editorial process diagram. The sequence explains decisions; it is not a performance rating.
Review the Image Before Using It
Inspect the complete image at useful viewing sizes. Look for distorted objects, confusing relationships, misleading symbols, stray text, and details that change the meaning. A polished visual can still contradict the article's explanation.
If the image includes an identifiable product, place, or person, assess whether the depiction could mislead readers into treating it as a factual photograph. Prefer neutral conceptual illustrations when exact identity is unnecessary.
Check the image alongside the caption and surrounding text. The page should not imply that an illustration is a screenshot, test result, or example of actual customer work. Give the reader enough context to interpret it correctly.
Prepare an Accessible Web Asset
Export a web-appropriate format, preserve the intended aspect ratio, and use dimensions that fit the page. Avoid loading a huge original when a smaller version is sufficient. Preview the crop on mobile before accepting the asset.
Write alternative text that explains the informative content rather than repeating the headline or stuffing keywords. Decorative images can have empty alternative text when they add no information, while meaningful diagrams need a useful textual explanation nearby.
The publishing guide explains the final asset check. Keep source screenshots, illustrations, and data visuals in their appropriate roles. A small collection of purposeful visuals is more useful than automatically filling every section with imagery.
Frequently Asked Questions
Should all blog images be generated?
No. Choose screenshots, photographs, diagrams, or generated illustrations according to the information the reader needs. Precise evidence should come from a real, appropriate source.
Can a generated image prove a product result?
No. A generated image can illustrate a concept, but it cannot establish a measured result, actual interface, or customer experience.
How specific should a prompt be?
Describe the subject, purpose, composition, placement, and style. Include exclusions that prevent misleading text, interface details, or decorative clutter.
Choose the Features That Fit Your Work
Use generated images for illustration. Use real sources and exact chart tools when the visual needs to establish a fact.
Explore Koala AI