Content Derivatives

Introducing Content Derivatives in PhotoShelter for Brands

Our Content Derivatives design brings the best of non‑destructive editing to the DAM: your master file remains pristine while every change is saved as a separate, linked asset. Because the relationship is tracked, teams can always audit the source of a published version and update it with confidence that they are not overwriting anything.

Treating each derivative as a first‑class file in the DAM also improves everyday tasks: derivatives appear in search results, can be permissioned, and are shareable and downloadable just like any other asset.

What Are Content Derivatives?

Crop, resize, and format change from the original.

A derivative is a new file you create from an original image by applying transformations like cropping, resizing, or changing the file format. You might turn a horizontal image into a square for Instagram, generate a smaller JPEG for the web, or export a high‑resolution TIFF for print. Each of those outputs becomes a unique asset you can manage like any other file in your library.

The key idea is that derivatives are meant for use “at the edges”—the places content is published—while the original remains your untouchable source of truth. You can create as many versions as needed for different channels, while retaining traceability back to the master file.

Because derivatives are stored in the Library, you don’t have to rely on local “save as” files that easily get lost, duplicated, or overwritten. You can search for and share them alongside originals, and apply the same permissions to them.

How are Derivatives stored in the Library?

Every derivative is a concrete file with its own file ID, metadata, and preview. This makes governance practical: derivatives appear in search results, can be tagged or captioned for their specific purpose, and can be permissioned or shared just like other assets. 
 

The original file is never altered (non‑destructive editing); you can always revert

Non‑destructive editing means your original remains exactly as it was uploaded; all changes are saved into separate derivative files. If a derivative needs to change, you edit the derivative—not the master. If you don’t like the result - say the crop is wrong, or you don't want to go with the chosen format, you can always create another derivative, all without putting the original at risk.
 

Derivatives act as digital presets, referencing the original plus transformation settings

Each derivative reflects its transformation choices—crop box, resize dimensions, and chosen file format—applied to the original at creation. That “preset” can be adjusted later if you need to refine a crop or change a format. Crucially, PSB still saves the derivative as a real file (not just a virtual rendition) to maximize compatibility across search, sharing, and permissioning.

Empowering your workflows with Content Derivatives

You can now save the results of cropping, resizing, or file conversion directly back into your library as derivatives. These are not one‑time downloads; they are reusable assets you can search, permission, and share like any other file. This cuts out the “export and re‑upload” loop that slows teams down and scatters files across desktops.

This change replaces older “crop on download” behaviors with a unified approach that saves outputs back to the DAM. Your Library remains the single place where content lives and evolves!

Use named presets to standardize sizes and formats for web, social, and print

Admins and editors can create named presets that bundle size, aspect ratio, and file format for repeat use. Presets make it trivially easy to pick the approved Instagram square, the standard web banner, or the media‑kit print size.

Create derivatives in batches for multiple images at once

Batch creation lets you apply a preset or a custom transformation to multiple images in a single operation. It’s ideal for event galleries and campaign sets, where you routinely need channel‑ready versions across dozens or hundreds of photos. After the batch runs, you can still fine‑tune individual crops as needed.

Batch actions are permission‑aware: you need upload rights to the destination gallery or workspace where derivatives will be saved. 

Things to consider:

This current Derivatives release covers images only. That focus lets teams immediately accelerate their most common publishing tasks while PSB continues to evolve video and document capabilities elsewhere in the product roadmap. It also ensures the core experience—cropping, resizing, converting, and saving back into the DAM—is polished and reliable from day one.

If your workflows require multimedia derivatives today, you can still use download options or external editing tools for unsupported types.
 

Derivatives must be created from the original, not from another derivative

To keep lineage simple and reliable, PSB disallows creating a derivative from an existing derivative. All derivatives attach directly to the original. This prevents confusing chains (crop of a crop of a crop).
 

Derivatives take up storage as real files

Unlike virtual versions, PSB derivatives are real files that consume storage. 

Benefits of using Content Derivatives

Speed

Derivatives slash the steps between “I have an image” and “I can publish it everywhere.” One‑click presets and batch actions eliminate repetitive exporting and re‑uploading, saving time for creative work.

Consistency

Presets turn brand rules into everyday defaults. Users don’t have to remember exact sizes, ratios, or formats; they pick from clearly named, approved choices. Outputs match your standards every time, even when created by new or infrequent contributors under deadline pressure.

Control and governance

Derivatives are searchable, shareable, and permissioned like other files, which means governance never leaves the DAM. Admins and brand leads retain visibility and control even as outputs multiply across channels. Parent/child links provide transparent lineage for audits and content reviews.
 

Reliability

When the original is updated or replaced, linked derivatives update automatically in the background. Direct links and embeds keep pointing to the right place, which reduces the risk of stale or mismatched imagery proliferating across channels. 
 
 

FAQs 
 

What file types are supported in this release?

This Q1 release supports image derivatives. Transforms include crop (freeform and common aspect ratios), resize (by pixel dimensions), and file format conversion to JPG, PNG, WebP, and GIF. These cover the vast majority of day‑to‑day needs for web, social, and basic print output.

If your workflow requires video, audio, or documents, you can continue using your existing tools and download options. The focus here is to deliver immediate, high‑impact value for images, where most teams spend the bulk of their time. As adoption grows, insights may inform future scope.

Using presets to encode approved formats avoids mismatches—e.g., accidentally using JPG where transparency is required. Clear names make the right pick obvious under deadline pressure.

Do derivatives replace the original file?

No. Derivatives never alter or replace the original; they are separate, linked files saved alongside your master. This is the essence of non‑destructive editing: the source of truth remains pristine, while outputs evolve independently for specific channels and uses.

If you need to change a derivative, you edit the derivative itself or create a new one. If you need to change the master, PSB updates linked derivatives automatically in the background to keep downstream uses current. That combination of safety and automation is what makes this workflow both fast and reliable.

The parent/child relationship is always visible in the file info panel, so you can audit and update with confidence.
 

Do derivatives count against storage?

Yes. Derivatives are real files and count toward your account’s storage. This choice improves compatibility across search, permissions, sharing, and background updates, and makes usage visible and auditable rather than hidden. 

To manage storage intentionally, save derivatives into known destinations—e.g., channel‑ or campaign‑specific galleries—so they are easy to find and archive when they’re no longer needed. 

Where should I save derivatives?

The best practice is to use channel‑ or campaign‑specific galleries—e.g., “/Derivatives/Social,” “/Derivatives/Web,” or “/Campaigns/Spring‑2026/Derivatives.” This keeps sharing simple and makes cleanup straightforward when a campaign ends. It also clarifies permissions for editors and partners working in those channels.

If you have any doubts, please ask your brand or Library Admin to define destinations and set the right upload permissions.

How is this different from destructive editing?