Where media lands in your repository
When media publishes, Acrosite commits it under public/images, with a folder per content type, and references it from your Markdown as a clean image path.
When media publishes, Acrosite commits it to a predictable place in your repository and references it from your Markdown with a clean path. This reference shows where images land and how they are referenced, so your site can serve them.
Who this is for
Developers connecting a site to Acrosite, and anyone curious where published images go.
Where media is committed
Acrosite writes media under public/images, with a folder per content type:
public/images # project media root
public/images/posts # Post images
public/images/pages # Page images
public/images/<type-key> # images for a Custom Content TypeKeeping media under public/images means image URLs stay clean and predictable. This mirrors the content paths described in Acrosite-managed content paths.
How images are referenced
In the generated Markdown, an image is referenced by a web path that drops the public prefix, because most frameworks serve the public folder at the site root:
So a file committed at public/images/posts/my-image.webp is referenced as /images/posts/my-image.webp. See Generated Markdown and frontmatter for how this fits into the published file.
Make your site serve the media
Build your site to serve images from public/images (or map that location during your build). If you use a framework that serves a public directory at the web root, the /images/... references will resolve with no extra work.