# Give the correct explanation for adding a suffix to image files names on upload

**URL:** <https://forum.bricksbuilder.io/t/give-the-correct-explanation-for-adding-a-suffix-to-image-files-names-on-upload/40663>\
**Category:** Feature Requests / Improvements\
**Created:** [October 20, 2026, 4:28pm UTC](https://forum.bricksbuilder.io/t/give-the-correct-explanation-for-adding-a-suffix-to-image-files-names-on-upload/40663 "2026-10-20T16:28:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![martin.sauter](https://forum.bricksbuilder.io/user_avatar/forum.bricksbuilder.io/martin.sauter/32/20805_2.png) [@martin.sauter](https://forum.bricksbuilder.io/u/martin.sauter)\
**Post date:** [October 20, 2026, 4:28pm UTC](https://forum.bricksbuilder.io/t/give-the-correct-explanation-for-adding-a-suffix-to-image-files-names-on-upload/40663/1 "2026-10-20T16:28:52Z")

</div>

Currently, if you upload an image in the Bricks media browser, you might get an error message like the following one:

> my-image-1200x900.webp already exists. Rename this file or upload it as my-image-1200x900-1.webp.

This explanation may be correct, but there are cases where it is misleading and technically wrong. WordPress also adds a number as a suffix if your original filename ends with dimensions in the format as in our example above.

The reason is that WordPress tries to avoid conflicts with thumbnails which have dimensions in their filename in exactly this format.

Documentation: [wp\_unique\_filename() – Function | Developer.WordPress.org](https://developer.wordpress.org/reference/functions/wp_unique_filename/)

So the error message should distinguish between these two reasons (or give both as an explanation why the filename is not accepted).
