Proxy Generation Overview
How Nomad Media automatically generates proxy versions of video, audio, and image assets for playback, preview, and downstream AI processing.
Proxy Generation Overview
When a file is ingested into Nomad Media, the system automatically generates proxy versions optimized for web playback, thumbnail display, and downstream AI processing. Proxies are stored separately from master files and are referenced automatically throughout the platform.
Proxy generation requires no manual intervention. It is governed by the Rules Engine, which means it can be scoped to specific folders and file types, and rules can be added or updated at any time.
Video Proxies
Default Behavior
By default, a video proxy is generated for any file that meets one or more of the following conditions:
| Condition | Default threshold |
|---|---|
| Video width | > 1920 px |
| Video height | > 1080 px |
| Bitrate | > ~2 Mbps |
| File extension | Not .mp4 or .webm |
The default proxy output is a single MP4 file. Without a proxy, users on slower connections or using standard web browsers cannot reliably play back high-bitrate or unusual-format source files in the Nomad UI.
Default Proxy Settings
Six primary settings control the output characteristics of the default video proxy:
| Setting | Default |
|---|---|
| Output format | MP4 |
| Max width | 1920 px |
| Max height | 1080 px |
| Frame rate | 30 fps (see note below) |
| Video bitrate | Set by MediaConvert template |
| Audio tracks | Passthrough (one-for-one from source) |
PAL / European content: The default frame rate is 30 fps (NTSC). If your content is primarily 25 fps (PAL), this setting should be changed during initial setup to avoid frame rate conversion artifacts.
Hundreds of additional MediaConvert transcode properties are available beyond these six defaults. Contact Nomad Media support to discuss custom profiles.
Additional Renditions
Beyond the default single MP4 proxy, additional renditions can be generated from the same ingest event using the same rules engine. Common options include:
- Additional MP4 sizes / bitrates — e.g., a lower-bitrate mobile proxy alongside the standard proxy
- HLS (HTTP Live Streaming) — adaptive bitrate streaming with multiple quality levels; web players automatically select the appropriate quality based on connection speed
- DASH (Dynamic Adaptive Streaming over HTTP) — an alternative adaptive streaming protocol
Each additional rendition type incurs additional transcoding and storage costs. HLS and DASH are particularly useful when content will be delivered to end users on variable internet connections.
Optional Video Proxy Settings
| Setting | Notes |
|---|---|
| De-interlacing | For broadcast / interlaced source content; prevents comb artifacts in the proxy |
| Audio track merging | Collapses multiple separated audio tracks into a single track; important if AI transcription will be enabled (see below) |
Audio track merging and AI transcription: AI subtitle and transcript generation analyzes only the first audio track of the MP4 proxy. If your source files contain separated audio tracks (e.g., tracks 1–4 each carrying independent audio), enabling audio track merging will consolidate them before transcription runs, producing significantly better results. See Transcoding for configuration details.
Audio Proxies
All audio files are proxied to MP3 by default. Audio proxy generation uses the same rules engine as video and can be scoped to specific folders or file types.
Dependency: An MP3 proxy is required before AI transcription, subtitle generation, or sentiment analysis can run on audio content. Enable audio proxying for any folder where AI audio processing is intended — even if the proxy is not needed for playback purposes.
Custom audio output formats and streaming audio versions are available on request.
Image Proxies
All images ingested into Nomad automatically receive two proxy outputs:
| Output | Default size | Format |
|---|---|---|
| Thumbnail | 300 × 300 px | JPEG (PNG files stay PNG) |
| Preview | 800 × 800 px | JPEG (PNG files stay PNG) |
Both are scaled to fit within their maximum dimensions while preserving the original aspect ratio. These defaults are configurable.
Adobe and PDF Files
- Adobe Illustrator / Photoshop files: Nomad does not render layers or composites. If the file was saved with an embedded preview (which Adobe applications include by default), Nomad extracts that preview and scales it to the configured proxy dimensions.
- PDF files: Nomad attempts to render the first page as a thumbnail. Success depends on the PDF's encoding — encrypted or non-standard PDFs may not render. Only the first page is used; multi-page PDFs are not fully rendered.
AI-Powered Smart Crop (ImageKit)
For use cases requiring multiple web-optimized image variants from a single master image — for example, auto-generating a mobile portrait crop and a desktop banner crop from the same source — Nomad integrates with ImageKit to provide AI-powered smart cropping. This is configured separately from standard proxy generation.
Storage and Cost
Where Proxies Are Stored
Proxies are stored in a separate S3 location from the master library. They do not appear in the same directory tree as source files and are referenced automatically by the platform. This keeps the master file structure clean and makes it straightforward to apply different access policies to masters vs. proxies.
Archiving note: When master files are moved to Glacier for cost savings, all proxies remain in hot storage. Users can continue to view thumbnails, play back proxies, and access all AI-generated metadata while the master is archived. See Media Archiving & Storage Lifecycle.
Storage Cost
Proxy storage typically adds 7–10% to your total library footprint, depending on proxy settings and the mix of content types.
Transcoding Cost
Video proxy transcoding is performed by AWS MediaConvert, running within your AWS account.
| Content type | Approximate cost |
|---|---|
| Video proxy (MP4) | ~$1.50–$2.00 per hour of video |
| HLS / DASH (additional renditions) | Additional cost per rendition |
| Audio proxy (MP3) | Minimal |
| Image proxies | Minimal |
Proxy generation is a one-time cost per file. Storage is ongoing. Because proxies are substantially smaller than master files, the storage overhead is typically modest relative to the total library size.
Related Pages
- Rules Engine Overview — how processing rules are structured and scoped
- Transcoding — frame rate, de-interlacing, multi-track audio, HLS/DASH, and MediaConvert profile details
- Reprocessing Assets — how to retroactively apply new proxy rules to existing content
- AI Enablement Guide — AI processor dependencies on proxy generation
- Search and Discovery — how transcript, subtitle, and deep-search experiences depend on processing outputs
- Phased AI Rollout — how to stage proxy-dependent AI features safely
- ImageKit Integration — AI-powered smart crop for images
- Media Archiving & Storage Lifecycle — storage cost optimization