Write captions for images when you add them
Most content systems let you add a caption when you upload an image. Most people skip it. They plan to come back later, after they've placed the image in the post. Later doesn't happen.
The caption field exists at upload time for a reason. That's when you still remember why you chose the image, what it shows, and how it connects to the content around it. Write the caption then.
Context disappears quickly
You're looking at the image file. You know what's in it. You know why it matters. You've just cropped it or resized it or renamed it. The work is fresh.
Come back three days later to add the caption and you're staring at a thumbnail in a media library. You'll write something generic because you've forgotten the specifics. Or you'll skip it entirely because you're in the middle of editing the post and don't want to break flow.
Upload time is when the context is sharpest. Use it.
Captions aren't alt text
Alt text describes the image for people who can't see it. Captions add context for people who can. They're different jobs.
A chart showing quarterly revenue needs alt text that describes the data. The caption might say "Revenue increased after the product launch in March." The alt text is neutral description. The caption connects the image to your argument.
If your CMS has both fields, fill both. If it only has one, write alt text first—that's for access. Then decide if you need a caption in the body copy itself.
Write captions as full sentences
A caption isn't a label. "Product dashboard" doesn't tell anyone why the image is there. "The dashboard shows three filters active by default" does.
Full sentences force you to say something useful. They also format better. A fragment in a caption field looks unfinished. A sentence looks intentional.
If you can't write a full sentence about why the image belongs in the post, you probably don't need the image.
Use the upload moment as a checkpoint
Adding a caption at upload time creates a natural decision point. If you can't explain why the image matters in one sentence, maybe it doesn't matter. Maybe you grabbed it because the post felt sparse, not because it added information.
That's useful feedback. It's better to realize the image is decorative before you've embedded it in three places and written transitions around it.
If the caption comes easily, you've confirmed the image is doing work. If it doesn't, you've learned something before you've committed.
Don't leave it for the next person
On a team, the person uploading the image often isn't the person writing the post. The uploader knows what's in the file. The writer knows what the post needs. Neither has full context for the caption unless they coordinate.
That coordination won't happen by accident. Decide who writes captions and when. If the uploader does it, they need to know what the image will illustrate. If the writer does it, they need to do it at placement time, not at the end during a final pass.
Leaving the field empty and hoping someone fills it later means it stays empty. Systems with required fields solve this. Systems without them rely on discipline.
Make captions part of image prep
If you're naming image files before upload, add caption writing to that same workflow. You're already looking at the file, thinking about what it shows. The caption is the next logical step.
Batch workflows make this easier. Upload ten images at once and you'll skip captions to get through the queue. Upload them one at a time as you prepare them and the caption becomes part of the preparation.
The goal isn't more process. The goal is writing the caption when you actually remember why the image matters.