A wrong Avada logo on mobile or after scrolling usually needs a state-by-state check, not another upload to the default logo field. Identify which header and image element actually render, then compare the image source and its displayed size.
Capture four states before editing
Use the same public page while logged out. Record the logo at desktop top, desktop scrolled, mobile top and mobile scrolled. Note whether the fault is the wrong artwork, a missing image, unexpected dimensions or blur. Those are different problems.
For example, a white logo can look missing on a white sticky background even though the image downloaded correctly. A sharp desktop logo with a blurry mobile copy suggests separate source or sizing choices. Neither observation establishes a cache failure.
Find the active image element
In browser developer tools, inspect the visible image. Read its source, natural dimensions and rendered dimensions. If responsive image selection is present, compare the browser's selected source as well. These are read-only checks; you do not need to change production markup in the console.
Avada's mobile and sticky header documentation distinguishes Header Builder image sources, screen-size visibility and sticky visibility. A custom Header Builder layout may use an Image Element instead of the default header's logo behavior. Open the layout assigned to that page, not merely a similarly named header template.
If a child theme changed the structure itself, start with the global header override diagnosis. Image sizing cannot repair a missing header element.
Source width: Example: 400 image pixels. Display width: Example: 200 CSS pixels. Clear space: Inspect padding inside artwork. Transitions: Scroll, rotate and open menu. Explanatory checklist, not a customer test result.
Match pixels to the intended width
For a simple explanatory example, a 400-pixel-wide raster logo intended to display at 200 CSS pixels provides a two-to-one source ratio. Setting its displayed width to 400 pixels removes that extra density. Avada documents using half the retina source width as the maximum display width for that setup.
Check the file itself for transparent padding. A 400-pixel canvas with a tiny mark centered inside it can still produce an apparently small logo. Crop or export the original artwork intentionally rather than compensating with huge CSS dimensions. Preserve the brand's proportions and approved clear space.
Repair one state, then verify the transitions
Change the source or visibility setting on the responsible element. Confirm that mobile and sticky variants do not both appear at the breakpoint. Scroll down and back up slowly, rotate the device and open the mobile menu. The logo should remain readable without covering navigation or shifting the header height unexpectedly.
Only after confirming saved settings should you invalidate the relevant generated styles or image cache. Use a versioned replacement filename when artwork changed but an old asset remains cached; avoid renaming every media file.
Close the task with the four-state comparison, the selected source and the rendered width. For overlapping navigation or a persistent builder mismatch, a focused header repair can address the responsible layout without rebuilding unrelated pages.
References reviewed October 14, 2026. Examples are explanatory, not customer test results.