Shipshot guide

How to prepare a clean status bar for app-store screenshots

The status bar is a small strip that quietly signals whether a set was prepared carefully. A low battery, a half-typed carrier name, a notification sliding in, or an inconsistent clock across frames all read as carelessness, and they are entirely avoidable with a few minutes of preparation before capturing.

Know what an untidy status bar looks like

The usual offenders are a battery at eight percent, a red recording indicator, a personal hotspot banner, an alarm icon, a carrier name that is a test SIM, a weak signal, and a clock that differs in every frame. None of them are fatal, but together they make an otherwise careful set feel improvised.

  1. Review each capture's top strip on its own before looking at anything else.
  2. List the icons that vary between frames in the same set.
  3. Treat any variation you cannot justify as something to fix.

Prepare the device before capturing, not after

Fixing the status bar in an image editor is slow and looks retouched. Fixing it before capture is fast and looks real. Charge the device or use a simulator, silence notifications so nothing appears mid-capture, disconnect anything showing a banner, and confirm the signal and network indicators look ordinary.

  1. Charge to a healthy level or capture from a simulator with a clean bar.
  2. Silence notifications and disable anything that produces a top banner.
  3. Recapture the whole set in one session so the bar stays identical throughout.

Keep it consistent across the set and the locales

Consistency matters more than any particular value. A set where the clock reads the same across every frame looks composed; a set where it drifts by seven minutes looks like a screen recording someone paused. The same applies across localized versions, where a recapture for one language can silently introduce a different battery level or signal strength.

  1. Use the same clock, battery, and signal state across every frame.
  2. Check localized versions against the source set for drift.
  3. Confirm consistency again after any single-frame recapture.

Do not let tidying become misrepresentation

A clean status bar is presentation. Removing or altering things inside the app to imply behaviour it does not have is not. Keep the edit at the level of the device chrome, and leave the interface, its content, and its state exactly as the app actually renders them.

  1. Limit tidying to the status bar and device chrome.
  2. Leave interface content and app state untouched.
  3. Re-read the frame and confirm it still shows a state the app can reach.

Review checklist

✓ No low battery, recording, hotspot, or alarm indicator is visible.✓ The carrier and signal indicators look ordinary rather than like a test rig.✓ Clock, battery, and signal match across every frame in the set.✓ Localized versions match the source set's status bar.✓ Tidying stopped at the device chrome and did not touch app content.

Questions to ask before handoff

Does the status bar actually matter?

Not on its own, but it is one of the fastest signals of whether a set was assembled with care, and inconsistency across frames is noticeable even to people who never consciously look at it.

Is it acceptable to edit the status bar afterwards?

It is presentation rather than product misrepresentation, but preparing the device first is faster and avoids a retouched look.

What if my app hides the status bar?

Then capture it as the app renders it and keep that consistent across the set. Do not add a status bar the app does not show.

Share this guide