Start with the outputs people actually need
A media repository can spend considerable effort preparing files that nobody uses. Before adding conversion capacity, establish which outputs serve a real workflow: editorial previews, approved downloads, publishing destinations, or downstream integrations.
The goal is a repeatable preparation process with clear access rules. A marketing preview and a production master may come from the same asset, but they do not necessarily need the same resolution, format, or availability.
Separate the master from its delivery formats
For each asset class, document the original format and the required derivatives. Record dimensions, output format, intended consumer, and when the derivative must be available. Treat that inventory as a delivery contract with the teams consuming the media.
Nuxeo's picture-conversion documentation describes configurable picture views, conversion chains, filters, and disabling default conversions. These are concrete places to examine when a repository produces unnecessary picture derivatives. Conversion filters operate with a detached document in a worker; do not design them around an interactive user's session. Removing a default conversion can also remove it from the available views in the UI. Nuxeo picture conversions
Change one part of the workload at a time
A useful review sequence is:
- Inventory generated outputs and identify their consumers.
- Capture a representative workload, including large and unusual files.
- Propose removing or narrowing one conversion that has no required consumer.
- Verify previews, downloads, and publishing integrations with the affected teams.
- Compare processing time, failure rates, queue delay, and output storage against the baseline.
Keep picture and video requirements distinct. Do not assume that a picture-conversion setting also controls a video pipeline.
Preserve access controls as you simplify processing
A derivative should have an explicit access policy. Do not assume that removing an output from a screen prevents someone from downloading it. Nuxeo documents download security policies for controlling access to particular renditions. Test the download path as well as the interface. Nuxeo rendition security
Define success before claiming savings
Agree on a measurable result: fewer conversions per ingested asset, less time waiting for a required preview, or lower processing cost for the same accepted outputs. Record the sample size and configuration with the result. A reduction measured on small photographs should not be presented as a guarantee for large video files.
For implementation help, see Maretha's performance optimization services and custom rendering per MIME type.
Work with Maretha
Working through a content platform challenge?
Bring your platform, constraints and questions. Let us help you work through the approach.
Discuss your project ↗