Skip to main content
Nuxt’s @nuxt/image module supports custom providers. Configure Tenbyte once and use <NuxtImg> (or <NuxtPicture>) anywhere in your app — Nuxt handles srcset, lazy loading, and sizing.

Prerequisites

  • Nuxt 3 with @nuxt/image installed:
  • A Tenbyte distribution with Image Optimizer enabled.
  • Your Tenbyte CDN hostname.

Configure the provider

nuxt.config.ts

Use <NuxtImg>

Nuxt resolves src against baseURL and emits a srcset with multiple widths. modifiers map to Tenbyte transform query params.

Use <NuxtPicture> for advanced fallbacks

<NuxtPicture> emits a <picture> with multiple <source> elements — one per format — for browsers that need explicit fallbacks.

Verify

Expected URLs include your transforms:

Tips

  • Use sizes — without it, Nuxt picks the largest width for every breakpoint.
  • Pin quality in modifiers — keeps bundle output deterministic.
  • format: 'auto' — lets the edge negotiate WebP / AVIF based on the browser’s Accept header.
  • Lazy-load by default — Nuxt’s default. Override with loading="eager" only above the fold.
  • Cache long. Set a long TTL on /path/to/images/* via cache rules; each variant is independent.

Reference

@nuxt/image documentation