diff --git a/documentation/docs/30-advanced/60-images.md b/documentation/docs/30-advanced/60-images.md
index 6471eb68b45e..b5726f59ef55 100644
--- a/documentation/docs/30-advanced/60-images.md
+++ b/documentation/docs/30-advanced/60-images.md
@@ -133,13 +133,77 @@ By default, enhanced images will be transformed to more efficient formats. Howev
[See the imagetools repo for the full list of directives](https://github.com/JonasKruckenberg/imagetools/blob/main/docs/directives.md).
-## Loading images dynamically from a CDN
+## `$app/images`
-In some cases, the images may not be accessible at build time — e.g. they may live inside a content management system or elsewhere.
+In some cases, the images may not be accessible at build time — e.g. they may live inside a content management system or elsewhere. SvelteKit provides a helper through `$app/images` to make it possible to load these images using best practices. In its simplest form, you pass an image url and the intrinsic width and height of the image to `getImage` and spread the result onto an `img` tag:
-Using a content delivery network (CDN) can allow you to optimize these images dynamically, and provides more flexibility with regards to sizes, but it may involve some setup overhead and usage costs. Depending on caching strategy, the browser may not be able to use a cached copy of the asset until a [304 response](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/304) is received from the CDN. Building HTML to target CDNs may result in slightly smaller and simpler HTML because they can serve the appropriate file format for an `` tag based on the `User-Agent` header whereas build-time optimizations must produce `