Optimizing Images in Gatsby with gatsby-plugin-image
Add gatsby-plugin-image to generate multiple image sizes, modern formats, and lazy‑loading placeholders at build time, improving performance without runtime overhead.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Add gatsby-plugin-image to generate multiple image sizes, modern formats, and lazy‑loading placeholders at build time, improving performance without runtime overhead.
Learn how to add a local image with Gatsby’s StaticImage component so the build creates multiple resolutions, serves WebP/Avif, and shows a blur placeholder.
Gatsby's image pipeline can generate responsive WebP/AVIF variants and blur-up placeholders automatically, but uncontrolled processing causes layout shift and slow builds. Scope sources, set explicit sizes, and verify srcset output.
Choose gatsby-plugin-image for automatic responsive images, lazy-loading, and WebP conversion. Avoid mixing with legacy gatsby-image to prevent import errors.
Learn when to use Page Bundles versus the global assets directory in Hugo to optimize image processing, reduce duplication, and improve site performance.
Behance separates lightweight metadata from heavy image files, uses lazy‑loading and CDN‑edge format switching to keep portfolios fast and high‑fidelity.
Learn how to use Docker multi‑stage builds to create tiny production images that contain only your compiled app and its runtime dependencies.
Learn how to split build‑time and runtime concerns in a Dockerfile to produce smaller, safer images and when to revisit the design.
Learn how to parse Behance v2 project modules, optimize image URLs, handle rate limits, and understand API constraints for building reliable integrations.