Why is Meta Ads still showing my old creative?

Quick answer: identify the delivered ad before replacing the creative again

Meta Ads can keep showing an old image or video when another live ad still references it, the ad uses an existing post, a placement has its own asset, an automated creative feature can select a variation, or the replacement never finished publishing and review. A screenshot of an old ad does not prove that the editor ignored your change.

Start with one real delivered impression. Record the immutable ad ID, creative or post ID, placement, device, country, impression time, and the Page or Instagram identity that displayed it. Compare that evidence with Ads Manager before making another edit, because repeated replacements can create more versions and make the source harder to trace.

• User symptom: someone sees an image, video, crop, or message that the team believes was replaced.
• Control level: ad, post, creative asset, placement customization, catalog, or automated variation.
• Time grain: the publish, review, eligibility, and impression timestamps around one replacement.
• Likely mechanism: another live object, old post identity, override, variation, incomplete publish, or stale preview.
• Decision produced: pause the correct object, publish the intended version, remove one override, or document a preview-only cache.

Keep old-creative delivery separate from cropping and destination problems

This diagnosis is about creative identity: the delivered impression uses an older image, video, copy combination, or post than the approved version. It is different from the correct asset being cropped differently across placements, or the correct ad sending a click to the wrong landing page.

It is also different from losing likes and comments after duplication. Social-proof loss asks whether a replacement received a new post ID; old-creative delivery asks which live ad or post still owns the visual that appeared. The same IDs help both investigations, but the symptom and corrective decision are different.

• Old creative: the wrong version or source asset is delivered.
• Placement cropping: the intended asset is delivered with a different frame or ratio.
• Wrong landing page: the visual is correct, but the destination route is not.
• Lost social proof: the new visual is live, but engagement stayed with another post ID.
• Stale preview: an editor or shared preview looks old while live impressions use the new version.

Freeze one affected impression with stable IDs and timestamps

Do not investigate from campaign names or a screenshot alone. Choose one affected impression and preserve the ad ID from the ad preview, delivery report, Page transparency surface, support evidence, or recipient report when available. Record the account time zone and the exact time the creative replacement was submitted, published, approved, and first observed live.

Then capture campaign and ad set IDs, ad status and effective status, creative ID, post ID, connected identity, format, destination, placement, device, and country. If the evidence came from a comment or customer screenshot, confirm that it belongs to the current campaign rather than a boosted post, old duplicate, or another ad account using similar branding.

• Immutable campaign, ad set, ad, creative, and post IDs.
• Last edit, publish, review, eligibility, and observed impression times.
• Page or Instagram identity plus ad account ID.
• Exact placement, device, region, format, and destination.
• A live preview or screenshot tied to the affected object where possible.

Inventory every live ad that can still reference the old asset

Search the active account by creative details and IDs, not just by the current ad name. An old ad may remain active inside a paused-looking campaign branch, a duplicated campaign, a different ad set, an automated rule scope, or another campaign that reused the same post. Include recently renamed, scheduled, archived, and partner-managed objects that delivered during the affected period.

Use delivery data to narrow the list. If the old visual appeared in one country or placement, filter impressions and spend for that slice and inspect every ad that actually delivered there. Pausing the most obvious new ad will not stop an older sibling that still has eligibility and budget.

• Current and recently active ads using the source image or video.
• Duplicates, drafts, scheduled ads, boosted posts, and reused existing posts.
• Other campaigns or ad accounts connected to the same business identity.
• Renamed or archived objects that still delivered inside the report window.
• Rules or third-party tools that can reactivate or republish ads.

Check post identity, placement overrides, and automated variations

At ad level, determine whether the creative was uploaded directly or selected through an existing Page or Instagram post. Editing an ad shell does not necessarily replace media owned by an existing post. Compare the delivered post ID with the intended source, and confirm which identity owns it.

Next inspect placement asset customization, flexible formats, dynamic creative, catalog fields, Advantage+ creative features, and any automated media enhancements. The default Feed preview may show the new asset while Stories, Reels, Audience Network, or a catalog item can still draw from a different source. Test the exact placement and device where the old version appeared.

• Existing-post ID versus newly uploaded creative ID.
• Feed, Stories, Reels, and other placement-specific media overrides.
• Flexible or dynamic combinations of media, text, and calls to action.
• Catalog product images, overlays, templates, and item-level media.
• Automated enhancements or variations that were not part of the approved brief.

Verify that the replacement was published, reviewed, and eligible

A saved editor state is not the same as a live ad. Check whether the change was actually published, whether the publish action returned an error, and whether the replacement created a new ad or creative ID. Review the status at campaign, ad set, and ad level rather than assuming a green parent campaign means the edited child is eligible.

Compare the last old-version impression with the new version's approval and first-delivery times. Some overlap can be explained by reporting delay, an impression served just before the status change, or a replacement that remained in Preparing or review while the old object was still active. A persistent stream of new old-version impressions after the replacement is eligible requires an object or configuration explanation.

• Confirm the publish completed without a partial error.
• Record whether the edit produced a new ad, creative, or post ID.
• Check Preparing, review, rejected, scheduled, and effective-status states.
• Compare impression time—not screenshot time—with the replacement timeline.
• Allow for reporting delay without using it to dismiss ongoing live evidence.

Separate a stale preview from real delivery

Ads Manager previews, shared preview links, browser tabs, messaging-app link cards, and screenshots can preserve an older render. Reopen the exact placement preview in a fresh session, but do not treat clearing a browser cache as proof that customer-facing delivery is fixed.

The decisive test is a new live impression or a supported delivery preview tied to the intended ad ID after the publish and approval timestamps. If only one operator sees the old version in the editor while delivery evidence shows the new asset, classify the issue as a preview or local-cache problem. If new impressions still carry the old creative, continue tracing the serving object.

• Refresh the exact placement preview after confirming the ad ID.
• Open shared links without relying on an old browser tab or cached thumbnail.
• Distinguish the time a screenshot was sent from the time the impression occurred.
• Use delivery evidence to decide whether the problem is local or live.
• Do not repeatedly republish solely to make one stale preview update.

Apply the smallest fix and verify the original failing combination

Once the source is proven, change only that layer. Pause the unintended ad, publish the incomplete replacement, select the correct existing post, remove one stale placement override, update the affected catalog item, or disable the specific automated variation. Avoid rebuilding the campaign when the campaign and ad set are not responsible.

Retest the same ad ID, placement, device, identity, and region that exposed the problem. Confirm the intended version is eligible and recording impressions, then watch for any further delivery from the old object. Preserve the old IDs and screenshots until the account has passed a reasonable verification window.

• Another live ad: pause the unintended object and confirm its impressions stop.
• Existing post: reference the approved post or create a controlled new post.
• Placement override: replace or remove only the affected placement asset.
• Catalog or automation: correct the source field or disable the proven variation.
• Incomplete publish: resolve the error, review state, or dependency and test again.

How an AdSpecIt-style audit helps trace old creative delivery

An AdSpecIt-style audit can inventory active and recently delivering ads across the hierarchy, then connect ad IDs, post and creative identity, placement behavior, automated features, status history, and performance. That broader view is useful when a team has many duplicates or reused posts and the visible editor does not reveal which object served the impression.

The useful output is a source-to-delivery map: identify the affected impression, prove the serving ad and creative IDs, locate the first configuration layer that diverges from the approved version, and recommend the smallest safe correction. That turns 'Meta keeps showing the old ad' into a verifiable decision instead of another blind replacement.