Write alt text and captions from the picture itself.
This one sends your image to a server to be described. It is held in memory for a second or two and never kept.
Get alt text for it in about a second. Paste works too.
Looking at the image…
This tool sends your image to a server to be described. It is held in memory for the second the request takes, never written to disk, and never kept afterwards.
Looks at an image and writes the sentence that should go in its alt attribute — what a reader who cannot see it would need to know. Drop one in and you have it in about a second.
Alt text is the accessibility job most often skipped, and the reason is friction rather than indifference. Writing forty descriptions for a page is dull work and an empty attribute takes no time at all. Removing the friction is most of the fix.
It describes only what is visible. It will not guess who someone is, where a picture was taken, or what a face is feeling — those are the inventions that make alt text worse than useless, because the person relying on it has no way to check.
The common case. A first pass that is accurate and needs light editing beats an empty attribute by a distance, and beats the alt text people write when they are bored of it.
WCAG requires a text alternative for non-decorative images. This gets you a real one per image rather than a filename.
Switch to caption and you get a sentence or two of context in a neutral publishing voice, for the text under the picture rather than inside the tag.
Descriptions of what is actually shown, written the same way each time — which matters more across two hundred listings than across one.
Or paste it. JPG, PNG, WebP, HEIC and AVIF, up to 8MB.
Alt text is one sentence under 125 characters, for the attribute. A caption is a little longer and written to be read alongside the picture.
It is accurate about what is in the frame and knows nothing about your context. If the image matters because of something off-camera, only you can add that.
Straight into the markup, the CMS field or the alt box wherever you are publishing.
Usually, and it is worth a glance regardless. It describes what is in the frame well. What it cannot know is why you chose the image — if a photo is there to illustrate a specific point, the alt text may need to say so, and only you know that.
No, deliberately. It will not name people, place the location, or describe what someone appears to be feeling. Those guesses are confidently wrong often enough to be dangerous in a description someone cannot verify.
It will tell you when an image carries no information, and the right answer there is empty alt text — alt="" — so a screen reader skips it entirely rather than reading out a description of a background swirl.
Because it is read aloud, in sequence, without the option to skim. Around 125 characters is the length most screen-reader guidance settles on. If an image needs more than that, it usually needs a caption or a description in the body text instead.
Yes — this is one of the few tools here that sends anything. Describing a picture needs a model too large to run in a browser tab. It is scaled down on your device first, held in memory for the second the request takes, and never written to disk or kept.
It writes in English by default. Paste the result into a translator if you publish in another language — a description translated well reads better than one written in a language the prompt did not ask for.