How to add text to a screenshot on iPhone

Adding text to a screenshot sounds simple. In practice, the built-in iOS markup tool makes it frustrating enough that most people skip it and write the context in the message body instead. Then the recipient has to read two things and mentally connect them.

A label on the screenshot itself is almost always clearer. Here’s how to do it well.

The built-in markup tool — and where it falls short

When you take a screenshot on iPhone, a thumbnail appears in the corner. Tap it and you get iOS’s markup editor: a set of drawing tools plus a text option.

The text tool works for rough, private notes. The problems start when you’re sharing:

• Font size is hard to control — the default is often too large or too small for the screenshot’s scale
• Colors are limited — you get a basic palette with no way to match your annotation to the content
• No positioning precision — labels drift to wherever you drag them without snapping or alignment
• The output looks rough — anyone who has received a screenshot with iOS markup annotations knows the aesthetic

For something you’re sending to a client, posting in a changelog, or using in a product doc, the built-in tool usually isn’t enough.

When text labels actually help

Not every screenshot needs annotation. Text labels add value when:

• Something specific needs to be called out — “this modal is missing on iPad” works better with “missing on iPad” written next to the element
• There’s a sequence to follow — numbered labels (1, 2, 3) guide the viewer through steps without needing a caption paragraph below
• The screenshot is going somewhere without accompanying text — a standalone image in a doc or Notion page needs to carry its own context

Text gets in the way when the screenshot is already self-explanatory, or when the label says what the screenshot already shows. If you’re labeling a button “Save button,” you’re not adding information.

Keeping text readable

The two most common mistakes with screenshot text:

Too long. A label that wraps to three lines is a paragraph, not a label. Aim for five words or fewer. “Crashes here” beats “This element crashes on iOS 17 when tapped quickly.”

Wrong contrast. White text on a light UI disappears. Dark text on a dark UI disappears. If you can’t see your label clearly at a glance, it’s not working. A subtle drop shadow or a filled background behind the text usually solves this.

Arrows plus labels

A label alone tells someone what to notice. An arrow plus a label tells them where to look and what it means. The combination is almost always more useful than either alone — especially when the element you’re pointing at is small or in a dense part of the UI.

A common pattern: draw the arrow first, position it pointing at the element, then add the label at the tail of the arrow. This keeps the label away from the element itself, which tends to be cleaner than text overlaid directly on top of a UI component.

When to annotate vs. when to crop

Before adding any labels, ask whether a tighter crop makes the annotation unnecessary. If the only thing in the frame is the problem, you may not need text at all.

Use annotation when the broader context needs to stay visible — when the viewer needs to see where something is within the larger UI, not just the element in isolation.

Use crop when the surrounding context is noise and the label would just be pointing at the only thing in the frame anyway.

What to skip

Avoid:

• Decorative text that says nothing (“Here’s the issue 👇”)
• Labels that duplicate what’s already in the screenshot’s UI text
• More than three annotations on a single screenshot — at that point, you need multiple screenshots or a numbered sequence

The goal is a screenshot someone can understand in three seconds. Text annotation either gets you there faster or adds friction. Keep it to what’s necessary.