Understanding Image Derivatives

Summary

Creating a derivative helps users maximize efficiency. With Derivatives, all the variations and image modifications are made in your Bynder portal during upload.  Bynder Admins can even set up permissions to allow users to download derivatives, including watermarked derivatives.

Dynamic Asset Transformations (DAT) give you even more flexibility. Instead of setting up predefined derivatives, you can create digital asset transformations on the fly. 

Users can even have derivatives made automatically; simply contact Customer Support to enable this time-saving feature.  

Note: Both custom and default image derivatives cannot be created for files that exceed 50000 pixels in a single dimension (either width or height). Please be aware that for files exceeding 25000 pixels, preview generation is currently subject to processing limitations and may not be available for all file types or sizes.

Understanding Default Image Derivative Dimensions

  • mini: 80x80 pixels
  • thul: 250x250 pixels
  • webimage: 800x600 pixels

Note: The resolution of your default derivatives may deviate slightly from the dimensions mentioned above, depending on the aspect ratio of your original images.

Understanding Custom Image Derivative Options

Users can customize the resolution of the derivatives in the portal. When creating a derivative with a custom resolution, Bynder uses the longer side to determine the output resolution. For example, an 800-by-600-pixel derivative will use the 800-pixel side for resizing. The 600-pixel side is scaled to the aspect ratio.

Note: Derivatives (custom or default) are not instantly available after upload. Derivatives become available after processing.

These custom derivatives can be set up in your portal:

  • Prefix (Derivative Name): Edit the name for clarity, but avoid using the following: 
    • Special characters such as - or / should be avoided, except for underscores and spaces (spaces will be converted to underscores if used in a URL).
    • Generic names like original, web, webimage, thul, or thumbnail should be avoided, as these are already used for the automatic default derivatives created for every asset in the background.
    • Duplicated prefix names should be avoided. For example, if there are two "Low_res" derivatives that differ only by the output file extension, each should have a unique Prefix name.
  • A custom DPI value for your derivatives can be configured. For instance, we can automatically generate a 300 DPI derivative of your original 600 DPI image file.
  • An automatic crop generates the derivative based on the image's focal point. The crop adjusts dynamically, ensuring that one of the longer sides of the desired aspect ratio reaches the image border while still outputting the required size.

  • Default dimensions and aspect ratio are preserved for use in your webshop. Bynder can resize the image to the longer side, and its aspect ratio, and the remaining canvas will be filled with blank space to meet your fixed dimensions.
  • Derivatives generated based on the filename of the original file. Using regular expressions (regex) we can configure derivatives to only be generated when the filename of the original file meets specific criteria.  For example, if you don't want a derivative to be generated when the filename of the original file contains an icon. For more information, see the section Using Regular Expressions (Regex) for Automation below.
  • Public? Makes derivatives publicly available for the Bynder API. These derivatives will not be visible to users unless the View and download public media derivatives permission is selected.

Note: If using the Mass Uploader, the asset's filename must start with the specified regex for the derivative to be created. The standard uploader does not require this.

  • Unique URLs for Derivatives: Each derivative—whether a standard preset or a custom crop—is assigned a Unique URL. This is a permanent CDN link that lets you embed the image directly on external platforms.
  • Accepted output formats (JPG, PNG, and TIFF) are used to generate the derivative file.
  • Recommended sizes: We recommend that your asset have the original size, large (JPG - 1024*786 - 300 DPI - RGB), and small (JPG - 640*480 - 72 DPI - RGB).
  • Color spaces (RGB/CMYK/inherit): 
    • The inherit option ensures that the embedded color profile in the uploaded file is used to generate the derivative. This way, the derivative will be generated with the right colors. Inheriting the color profile is the best way to ensure the derivative's color profile matches the original file's. If you want to use this option, make sure you upload files with embedded color profiles.
    • If no embedded color profile is available in the uploaded file, the system will fall back to a default color profile. For the RGB color space, this will be the sRGB color profile. For the CMYK color space, users can set a custom fallback color profile for you. If no custom fallback profile has been set up, the system will default to the ISO Coated v2 300% (ECI) profile. 
    • PNG derivatives can be customized to preserve transparency, while JPGs can be set to the desired quality.

Note: Aside from Vector files, Bynder can not create derivatives with larger dimensions than the original file as it would lead to quality loss. Vector file types are AI, SVG, PDF, and EPS.

Using Regular Expressions (Regex) for Automation

In Bynder, you can use regex to control when specific image derivatives are automatically created. This is highly beneficial if you want to ensure only specific files trigger a transformation process.

What is Regex?

In simple terms, Regex (short for Regular Expressions) is a smart, automated way to search for and identify specific patterns in text. Think of it like a "Find" tool on steroids: instead of just searching for one specific word, you can tell the system to look for any file name that follows a specific structure—like all files starting with "2026_" or all files containing "Logo" followed by a number.

Examples of Regex Patterns

^2026: The caret (^) symbol tells the system to look at the very start of a file name. This would find "2026_ProjectA.jpg" but ignore "Report_2026.pdf."

\.png$: The dollar sign ($) tells the system to look at the end of a file name. This would identify any file ending specifically with ".png."

.*_Icon: The .* acts as a wildcard, meaning "anything can be here." This would find any file name that ends with "_Icon," regardless of the preceding text (e.g., "Web_Icon," "Print_Icon," or "Social_Icon").

How to Apply It

When your Admin configures a custom derivative in your Bynder portal, they can enter a regular expression pattern in the designated field. By doing so, you ensure that your automation is precise—applying specific settings only to the files that actually need them. For example, if you only want a "Watermarked" version created for files that contain the word "Public" in the file name, a regex rule ensures any file without "Public" in its name skips that processing step, keeping your workflow clean and your storage organized.

Note: If using the Mass Uploader, the asset's filename must start with the specified regex for the derivative to be created. The standard uploader does not require this.

Allowed Types

By default, derivatives will be created for nearly all image assets. If you want to create derivatives for selected asset types only, enter the types in the field. We recommend using the following types: PSD, BPM, EPS, JPG, TIF, TIFF, AI, PNG.
Note: When adding JPG as an allowed type, no derivative will be created if the original file has the JPEG file extension. Make sure to add JPEG as an allowed type so derivatives can be created for files with the JPEG extension as well. Vice versa, the same logic applies. TIF and TIFF are other examples.

CMYK Fallback Color Profiles

Setting value Profile description
Coated_FOGRA27 Coated FOGRA27 (ISO 12647-2:2004)
Coated_FOGRA39 Coated FOGRA39 (ISO 12647-2:2004)
ISO_Coated_v2 ISO Coated v2
ISO_Coated_v2_300 ISO Coated v2 300%
ISO_Uncoated_Yellowish ISO Uncoated Yellowish
Japan_Color_2001_Coated Japan Color 2001 Coated
Japan_Color_2001_Uncoated Japan Color 2001 Uncoated
Japan_Color_2002_Newspaper Japan Color 2002 Newspaper
Japan_Web_Coated Japan Web Coated (Ad)
PSO_Coated_300_NPscreen_ISO12647 PSO Coated 300% NPscreen ISO12647
PSO_Coated_NPscreen_ISO12647 PSO Coated NPscreen ISO12647
PSO_LWC_Improved PSO LWC Improved
PSO_LWC_Standard PSO LWC Standard
PSO_MFC_Paper PSO MFC Paper
PSO_SNP_Paper PSO SNP Paper
PSO_Uncoated_ISO12647 PSO Uncoated ISO12647
PSO_Uncoated_NPscreen_ISO12647 PSO Uncoated NPscreen ISO12647
SC_paper SC paper
Uncoated_FOGRA29 Uncoated FOGRA29 (ISO 12647-2:2004)
US_Sheetfed_Coated_v2 U.S. Sheetfed Coated v2
US_Sheetfed_Uncoated_v2 U.S. Sheetfed Uncoated v2
US_Web_Coated_SWOP_v2 U.S. Web Coated (SWOP) v2
US_Web_Uncoated_v2 U.S. Web Uncoated v2
Web_Coated_FOGRA28 Web Coated FOGRA28 (ISO 12647-2:2004)

Considerations

  • AI and PDF

    Bynder supports RGB derivatives for AI and PDF files. CMYK derivatives or derivatives that inherit the color profile of the original file cannot be created when the original file is an AI or PDF file.

  • DNG

    We cannot create derivatives for a DNG file if the original DNG file does not contain a preview file. Derivatives are based solely on the preview file.

  • TIFF When the original file is a TIFF file, the transparency cannot be preserved if:

    • The file includes transparent clipping paths, which often occur when the TIFF file is saved in Adobe Photoshop.
    • The TIFF file contains more than one alpha channel or a custom alpha channel.
    • The ExtraSamples metadata field of the TIFF file contains an unsupported value, such as Unspecified. 
    • Only one of the following two values is supported: 
      • Unassociated alpha
      • Associated alpha

    FAQs

Level: Proficient

Proficient-level articles are for users who have some prior Bynder knowledge. These articles require you to know the basics and may also require higher-level portal rights to accomplish the task outlined within the article. 

Updated