This guide explains how to configure upload settings in Scaleflex DAM, including how to handle duplicate files, duplicate filenames, image optimisation on upload, and automatically create variations. By the end, you’ll know how to set each option to best fit your upload workflow.
Note: Only users with the Owner, Administrator, Manager or Developer role can view or modify these settings. If your account doesn’t have these permissions, please contact your DAM Administrator.
Path: Settings → Library → Storage → Upload tab
Duplicate file content handling
Use this section to define what happens when a user tries to upload a file that already exists in DAM
Accept
Uploads the new file even if a duplicate exists.
Refuse
Cancels upload when a duplicate file is detected.
Important: DAM automatically cancels uploads of files that already exist in the same folder with the same name and identical content.
The settings above only apply when the user tries to upload a file which already exists in DAM in terms of image content, however there is an attempt to upload it under a different filename or in a different folder.
Duplicate filename handling
Action setting defines what happens if a user tries to upload a file with the same name as an existing one in the container :
Refuse
If you upload a file named test.jpg and then try to upload another file with the same name, the system will block the second upload.
Overwrite
If you upload a file named test.jpg and then upload another file with the same name, the old file will be deleted and the new file will take its position. Please note that deleted files can not be restored in DAM, if this option is chosen.
New Version
If you upload a file named test.jpg again, the system will update it with the new file. The old version would remain in the History tab and you would be able to restore it in case of need.
Tip: Use "New Version" if your team regularly updates images but wants to keep old versions for reference.
In the section File name you can define what to be the DAM behavior when someone tries to upload a new image content with a filename that is currently existing:
- Assign a random file name in UUID format will keep the old image with its filename and the new image will be renamed to 6638763c-8446-11ec-a8a3-0242ac120002 (for example)
- Keep the original file name with random suffix will keep the old image with its filename and the new image will be renamed to some_image_jsvYTvh.jpg (for example)
-
Keep the original file name will replace the old image with the new image content
Image optimisation on Upload
When you enable Optimize images on upload, every time a user uploads an image, the system will automatically resize it according to the rules you set (for example, max width 2000px and max height 2000px). This helps keep images lighter and more web-friendly without needing manual optimisation.
When you enable Create asset variations on upload, the system will automatically generate different versions of the same image at upload time, based on the presets you have configured (for example, smaller sizes, cropped versions, or formats like WebP). This is useful if you want to have ready-to-use versions for different use cases.
For Background Removal Target Folder, you can decide where the new version (the image with the background removed) will be stored. It can either go into an internal hidden folder (so it doesn’t mix with your main assets) or into the same folder as the original image. The choice depends on whether you want to keep the background-removed versions separate or alongside the originals. Please note that the internal hidden folder is not accessible via the Folder view in DAM.
Contact us
If you encounter unexpected behavior, contact our Support Team at hello@scaleflex.com and include:
-
Your organisation name and DAM token
-
The setting you’re trying to configure
-
A short description of the issue
Comments
Please sign in to leave a comment.