Assets & tasks / MERCHANT WORKFLOW
Why Can Reusing an Image Filename Cause Square Online Pictures to Swap or Fail to Load?
Square explicitly recommends giving every image uploaded to its site editor a unique filename to avoid unexpected behavior such as images swapping places or failing to load. That is a documented filename-identity precaution, not proof that every stale Square Online image is caused by a duplicate name. First identify the affected section and image record, then replace the intended asset with a uniquely named approved file and inspect the published page.
Identify the image and the section it belongs to
Square's Add images and backgrounds to your online store help distinguishes foreground images from section backgrounds. Both can be edited and replaced, but the controls differ.
The same help warns that image filenames should be unique before upload. If two campaign files both arrive as hero.jpg, their filenames do not distinguish which product, revision, or section the merchant intended.
However, the official warning does not explain Square's internal storage or caching implementation. Do not claim that a particular filename collision necessarily overwrites a specific stored object. Record the actual image identities and observed behavior before assigning a cause.
For a foreground image, Square documents selecting the image and choosing Replace. For a background, it documents Customize, Background, then the relevant Replace control. The merchant must identify which role contains the wrong picture before editing.
Prepare a collision-resistant replacement
Keep the approved original and create a destination-specific filename containing a meaningful product identifier, placement, and revision. For example, TEA-GRN-01-home-hero-v3.jpg is easier to distinguish from TEA-BLK-01-home-hero-v2.jpg than two files named hero.jpg.
This naming convention is CartVisual editorial guidance, not a required Square filename schema. Square's documented requirement is that each image have its own unique filename before upload.
Use a non-destructive copy of the page or a controlled draft where available. Replace only the affected section image. Save and publish through Square Online's documented workflow, then inspect the public page rather than treating the editor thumbnail as proof of publication.
Record the old and new filenames, intended section, asset content, saved state, and public observation separately. If the merchant cannot identify the correct section, stop before replacing unrelated images.
Hypothetical tea campaign with duplicate names
Hypothetical exercise; no Square Online site or upload was tested. A fictional merchant has two teas: SKU TEA-GRN-01 and SKU TEA-BLK-01.
The original source folders each contain a different file named hero.jpg. The green-tea photograph shows a pale green tin; the black-tea photograph shows a charcoal tin. The merchant plans to use them in separate homepage sections.
Before uploading, the team prepares uniquely named copies TEA-GRN-01-home-hero-v3.jpg and TEA-BLK-01-home-hero-v2.jpg. The expected public result is that each section displays the intended tin. No result is recorded.
| Section | Ambiguous input | Planned unique file | Actual state |
|---|---|---|---|
| Green tea hero | hero.jpg | TEA-GRN-01-home-hero-v3.jpg | Not uploaded |
| Black tea hero | hero.jpg | TEA-BLK-01-home-hero-v2.jpg | Not uploaded |
Choose the next action from the actual discrepancy
If the editor's selected image is already wrong, correct that section's image assignment using the unique approved file. A browser cache investigation is premature when the wrong asset is selected in the editor.
If the editor shows the correct new file but the public site still shows the old photograph, verify that the site was published and that the public page and section match the edited record. Preserve the observed URL, time, and visible revision difference for further delivery diagnosis.
If an image fails to load, inspect the actual selected file, supported format, and saved state. Square supports JPG, PNG, and GIF for website-section images. A filename warning alone does not establish the cause of a failed network resource.
The published-image diagnosticPhotoshop naming guide
CartVisual does not manage Square's site editor, resolve its image identity internally, or publish replacements.
Use the example with your own product records
The filled records are hypothetical editorial examples. The entry-template row is for your own files, settings and observations; it does not connect to another application.
| Fictional SKU | Website section | Original ambiguous name | Proposed unique filename | Actual editor selection | Actual publication state | Actual public image | Next action |
|---|---|---|---|---|---|---|---|
| TEA-GRN-01 | Green tea hero | hero.jpg | TEA-GRN-01-home-hero-v3.jpg | Not checked | Not published | Not inspected | Replace correct section and verify |
| TEA-BLK-01 | Black tea hero | hero.jpg | TEA-BLK-01-home-hero-v2.jpg | Not checked | Not published | Not inspected | Verify separate section identity |
What the sources establish
- Square Support — Add images and backgrounds to your online store: Verified unique-filename warning, supported formats, foreground/background replacement controls, and Save/Publish distinction.
Sources and further reading
Recorded source-review dates are listed individually below. An undated source does not inherit the article’s publication date. Software and platform rules can change; check the current original before acting.
- Square Support — Add images and backgrounds to your online store · Review date not separately recorded
Frequently asked questions
Does Square explicitly recommend unique filenames?
Yes. Its official website-image instructions recommend unique filenames to avoid unexpected image swapping or loading problems.
Does an old public image prove a filename collision occurred?
No. Verify the selected section image, saved publication state, and actual public delivery before assigning the cause.
YOUR NEXT CAMPAIGN
Create assets from a clear source
Bring your reviewed source photo or brand brief to CartVisual. Check the current tools, account access and credits before generating, then compare every result with your source.
Create a CartVisual account Open the workspace Check access and credits