Shop moved to shop.com: fix AI clips with a shop.app link on screen

If an AI clip shows or speaks a shop.app address, the redirect will not save it: text burned into pixels never redirects. Shopify moved Shop's web experience to shop.com on September 29, 2026, so re-render those clips from a clean source with the new address, and leave the rest alone.

This post covers the clip side only. Your links in descriptions, bios and ads are a separate fix, and Shopify's note covers them.

It is a small change, but small domain changes are exactly where old creative hides. A clip made in the spring can still be running in a paid ad set in the autumn, and nobody remembers what its end card says.

What exactly changed at Shop?

The changelog entry says Shop's web experience now lives at shop.com instead of shop.app, that existing shop.app links redirect automatically, and that stores, products and channel settings are unchanged. It recommends updating publicly shared links, such as social bios and ads, at your convenience because the redirects persist. No merchant action is required.

The word to notice is "links." A hyperlink in a caption redirects. A shop.app address drawn into a video frame, or read aloud by a voice, is just text and sound.

Which of my clips are affected?

Only clips where the old address is part of the media. Three cases come up:

• Burned-in end cards or lower thirds that show a shop.app address.
• Burned-in captions of a spoken line that says "shop dot app."
• Avatar scripts that tell the viewer to find you at the old address.

How do I put the new address on an existing clip?

Standalone video captions can burn authored overlay copy with cues (text plus start and end seconds) and skip speech-to-text, so you can add a short end card to a finished public clip. It needs a clean source: captions burn text on, and the docs do not describe removing text that is already in the picture.

A job up to 60 seconds is a fixed $0.20 of Sume usage under the current estimate, so confirm live pricing in GET /v1/catalog before a big batch. For avatar videos, inline captions leave a clean primary video_url and can soft-fail, which is why keeping the clean file matters.

curl -X POST https://api.sume.com/v1/video-captions \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: shop-com-endcard-001" \
  -d '{
    "video_url": "https://media.sume.com/artifacts/example/clean.mp4",
    "style": "slam",
    "cues": [
      { "text": "Find us on Shop", "start": 6.0, "end": 8.0 }
    ]
  }'

What if I only have the burned-in version?

Then regenerate or re-export from the project source. Sume does not edit text out of a rendered frame, and we do not suggest a crop that hides it, because it changes the framing you tested.

A practical rule: keep the clean MP4 for every clip that gets captions, and name the files so you can tell which ones carried an address. Next time a domain changes you will only touch the overlay.

If you use avatar videos, rewrite the script line instead of patching the caption. Spoken words and burned-in text should agree, and a caption that says one address while the voice says another reads as a mistake. Avatar Video scripts need an estimated 4 to 60 seconds, so adjust the lengths when you swap the line and check the estimate holds.

How do I find the clips that need work?

Keep a sheet of clips with a column for "address on screen or spoken." If you do not have one, video inspect can return the transcript and sampled stills of a clip on media.sume.com, which is enough to spot a spoken or drawn address without watching each file. It is billed by its own compute plus, when you ask for the transcript, a per-minute rate, so sample the clips most likely to carry an address first.

Anything posted weeks ago with the old address and a link in the caption is fine as it is; the redirect keeps working per Shopify's note.