Metadata inheritance for custom image derivatives

Summary

With this feature, specific metadata fields from the original asset can be automatically included in custom image derivatives. This helps keep important details, such as copyright and authorship, consistent throughout the process, whether the asset is shared through the API, public links, or direct downloads.

Who?

This feature requires your Customer Success Manager to enable this. This is an opt-in feature and is disabled by default to ensure you have full control over your metadata delivery.

Once enabled, users with permissions to Manage Presets or perform Asset Downloads/Crops will automatically see these metadata fields preserved in their generated files.

Why?

With metadata inheritance, you can:

• Ensure compliance: Keep copyright and license information attached to assets wherever they are used online.

• Improve SEO & tracking: Preserve titles and descriptions within the file header for better indexing and internal tracking.

How?

Metadata in Cropped Assets

Any derivative created using the Crop functionality—whether downloading a custom crop, creating a new derivative, or saving as a new asset—will also inherit the fields listed above.

Note: While the original Title metadata is included in the file header of a crop, the actual display title for cropped images in the Bynder UI will match the text input provided during the cropping process.

Technical Information

Refer to the table below for a breakdown of the supported metadata fields and their corresponding technical sources.

Best practices

Format Constraints: IPTC metadata writing is limited for WebP and not supported for AVIF formats.

No Custom Mapping: Inherited metadata fields are fixed to Title, Description, Author, and Copyright. Customization is not available.

Portal Overrides: If your portal overrides embedded metadata, Bynder-specific values will not apply to DAT derivatives; only original embedded data is inherited.

Check Your Output: Always check DAT URL metadata headers for correct fields when integrating with third parties.

DAT Derivative: While the use of metadata inheritance for custom image derivatives provides additional data context, it is not recommended for the Dynamic Asset Transformation (DAT) derivative as it can significantly impact delivery performance, increasing file size and latency. Please reach out to the team to confirm if your portal is a good candidate for this feature.

Updated April 14, 2026 10:03