# NO BUG: ACF dynamic background image missing in builder but works on frontend (2.4.4)

**URL:** <https://forum.bricksbuilder.io/t/no-bug-acf-dynamic-background-image-missing-in-builder-but-works-on-frontend-2-4-4/40735>\
**Category:** Bugs\
**Tags:** v2-4-4\
**Created:** [October 30, 2026, 7:15am UTC](https://forum.bricksbuilder.io/t/no-bug-acf-dynamic-background-image-missing-in-builder-but-works-on-frontend-2-4-4/40735 "2026-10-30T07:15:29Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![paulrbrierley](https://forum.bricksbuilder.io/letter_avatar_proxy/v4/letter/p/3d9bf3/32.png) [@paulrbrierley](https://forum.bricksbuilder.io/u/paulrbrierley)\
**Post date:** [October 30, 2026, 7:15am UTC](https://forum.bricksbuilder.io/t/no-bug-acf-dynamic-background-image-missing-in-builder-but-works-on-frontend-2-4-4/40735/1 "2026-10-30T07:15:30Z")

</div>

**Browser:** Chrome 156  
**OS:** Windows  
**Bricks version:** 2.4.4  
**ACF:** Image fields on custom post types

### Issue

ACF dynamic background images no longer display in the Bricks builder, although they render correctly on the frontend.

These backgrounds previously displayed correctly in the builder. No intentional changes were made to their configuration. The issue was noticed following a recent Bricks update, although we cannot confirm that the update caused it.

### Observed behaviour

- The background image control displays “Dynamic data is empty”.

- The background image is absent from the builder canvas.

- The same ACF image field renders correctly in a standard Image element.

- The dynamic background renders correctly on the frontend, including its CSS filters.

- The discrepancy occurs in two separate Single templates using different ACF image fields.

- Both the ordinary dynamic tag and its `:url` variation have been tested without resolving the issue.

### Expected behaviour

Dynamic background images should render in the builder as they do on the frontend.

### Relevant configuration

The background is applied to a Block element using Bricks’ native dynamic-data selector and an ACF image field.

Example configuration with a generic field name:

```auto
{
  "_background": {
    "size": "cover",
    "position": "center center",
    "image": {
      "useDynamicData": "{acf_example_image}",
      "size": "large"
    }
  }
}

```

### Additional observations

The builder applies the element’s positioning and CSS filters, but the `background-image` declaration is absent.

This appears to be a builder preview or dynamic-data resolution discrepancy rather than a frontend rendering problem.

The affected website is confidential and currently in development, so public screenshots and URLs cannot be provided. A sanitised reproduction may be possible if required.

---

<div class="post-metadata">

**Author:** ![timmse](https://forum.bricksbuilder.io/user_avatar/forum.bricksbuilder.io/timmse/32/1192_2.png) [@timmse](https://forum.bricksbuilder.io/u/timmse)\
**Post date:** [October 30, 2026, 7:37am UTC](https://forum.bricksbuilder.io/t/no-bug-acf-dynamic-background-image-missing-in-builder-but-works-on-frontend-2-4-4/40735/3 "2026-10-30T07:37:13Z")

</div>

Hi Paul,  
Welcome to the forum!

Could you temporarily select a freshly uploaded image in the affected ACF field and check whether its background appears in the builder? I reproduced the same symptoms locally when WordPress attachment metadata (image sizes) was missing (this can be due to a variety of reasons.).

In the Bricks Media Manager, select the affected image and choose **“Regenerate image sizes”**. This also rebuilds its WordPress attachment metadata. Once completed, reload the builder and check whether the dynamic background appears.

---

<div class="post-metadata">

**Author:** ![paulrbrierley](https://forum.bricksbuilder.io/letter_avatar_proxy/v4/letter/p/3d9bf3/32.png) [@paulrbrierley](https://forum.bricksbuilder.io/u/paulrbrierley)\
**Post date:** [October 30, 2026, 8:32am UTC](https://forum.bricksbuilder.io/t/no-bug-acf-dynamic-background-image-missing-in-builder-but-works-on-frontend-2-4-4/40735/4 "2026-10-30T08:32:21Z")

</div>

Thanks for the suggestions. I’ve made some interesting progress.

Rather than uploading a replacement image or regenerating image sizes, I tried the following:

1. Opened the affected custom post in the WordPress editor.

2. Clicked the edit pencil on the existing ACF image.

3. Clicked **Update Image** in the WordPress image dialogue, without making any changes.

4. Refreshed the Bricks builder.

**The dynamic background image reappeared in the builder.**

I repeated the same procedure on the second affected Single template, using a different ACF image field, with the same successful result.

Both background images now display correctly in the builder. No changes were made to the Bricks configurations, ACF field assignments or image files.

This resolves the immediate problem, but I’m curious about the underlying cause.

Does clicking Update Image refresh attachment metadata or trigger some other process that might explain the behaviour? Could this be related to how Bricks resolves or caches dynamic background images?

Thanks again for your help!

---

<div class="post-metadata">

**Author:** ![timmse](https://forum.bricksbuilder.io/user_avatar/forum.bricksbuilder.io/timmse/32/1192_2.png) [@timmse](https://forum.bricksbuilder.io/u/timmse)\
**Post date:** [October 30, 2026, 2:06pm UTC](https://forum.bricksbuilder.io/t/no-bug-acf-dynamic-background-image-missing-in-builder-but-works-on-frontend-2-4-4/40735/6 "2026-10-30T14:06:21Z")

</div>

Thanks for confirming that both backgrounds are displaying again.

Clicking “Update Image” in the ACF dialog reselects the attachment and refreshes the field preview; it isn’t the same operation as regenerating image sizes, so we can’t conclude that it rebuilt the image metadata.

Bricks does cache dynamic background lookup results during the Builder session, including unsuccessful results. Reloading the Builder starts a fresh lookup, but your result alone doesn’t establish whether metadata, cached data, or another update hook caused the recovery.

If it happens again, please let us know before repeating the workaround. A minimal sanitized reproduction with the affected template and ACF field would help us identify the cause.

As things stand now, however, I would consider the problem solved/no Bricks bug for the time being 🙂
