What is a Fallback Image?
A fallback image is a substitute shown when preferred visual content cannot be loaded or rendered. It may replace a missing image, failed video preview, unsupported format, or unavailable remote resource.
How Fallback Images work
A fallback is part of an interface's failure and compatibility design rather than merely another source URL. Selection may happen declaratively when the browser evaluates candidate formats, or imperatively after a chosen request or decode fails. The substitute should retain the intended semantic role and geometry even when it cannot reproduce the missing visual. It belongs in the rendering layer, while monitoring and asset repair address the underlying delivery problem.
Image software decodes the source into pixels, applies spatial or color operations, and encodes the result. Resize filters, crop coordinates, operation order, and output settings determine both appearance and file size.
Image operations interact with resolution, aspect ratio, alpha, color profiles, orientation, and compression. Test the complete sequence because changing the order of resize, crop, sharpen, and encode operations can change the result.
Key facts
- 1The final img element in a picture supplies a selection fallback when source rules or formats do not match. A network failure for the selected candidate does not reliably try every earlier candidate.
- 2An error handler that replaces src must avoid assigning the same failing URL repeatedly. Removing the handler or tracking attempted sources prevents an infinite sequence of error events.
- 3Explicit width and height or a stable aspect ratio reserves layout before either source loads. Alternative text should describe the image's meaning, not merely announce that loading failed.
When Fallback Images matter
Developers select fallbacks that preserve layout dimensions and communicate unavailable content clearly. Missing intrinsic dimensions can still cause layout shifts even when a substitute loads.
- Generating responsive website images, thumbnails, avatars, social cards, and product imagery.
- Standardizing user uploads to safe dimensions, formats, and metadata policies.
- Applying crops, overlays, watermarks, background operations, or visual analysis at scale.
Working with image at scale
Guidance that holds across every image term in this glossary, not just Fallback Images.
What you gain
- One source can produce consistent variants for different layouts and devices.
- Automated optimization reduces bytes without requiring editors to prepare every derivative.
- Explicit transformation rules make crops, dimensions, and formats reproducible.
What it costs
- Smaller dimensions and stronger compression reduce transfer size but can remove useful detail.
- Automatic crops scale well but can cut off important subjects when detection or focal information is wrong.
- Wide-gamut, HDR, and transparent assets need an end-to-end path that preserves those properties.
Answer these before production
- 1Test representative dimensions, transparency, color profiles, orientation, and animated inputs.
- 2Compare visual quality at the actual display size, not only at 100% zoom.
- 3Set explicit crop, fit, and upscaling rules so edge cases remain predictable.
How Transloadit helps with Fallback Images
When Fallback Images are relevant to your workflow, you can hand the surrounding image work to Transloadit instead of maintaining the processing stack yourself. Transloadit can resize, crop, optimize, convert, watermark, analyze, and generate images through declarative Assembly Steps, while preserving originals for future processing when needed.
Support for a specific codec, container, parameter, or combination can vary by Robot and processing stack. Check the linked documentation for the exact inputs and outputs available for your use case.