On this page
Project Setup

Acrosite-managed content paths

Where Acrosite writes Posts, Pages, Custom Content Types and media in your repository by default, and how to change the folders and file type for each content type.

ReferenceFor DevelopersUpdated June 7, 2026

When Acrosite publishes, it writes content and media into folders in your repository. Every project starts with the default folders below, and you can change them for each content type to match your site. This page shows where files land and how to change it.

Who this is for

Developers connecting a site to Acrosite, and anyone curious where published files go.

The default paths

By default Acrosite saves generated content inside a dedicated acrosite/content folder so developers can identify Acrosite-managed files, and writes media under public/images to keep public image URLs clean:

Paths
acrosite/content/posts      # Posts
acrosite/content/pages      # Pages
acrosite/content/<type-key> # each Custom Content Type
public/images/<type-key>    # media for each content type

Each Post, Page, or Custom Content Type item is committed as one MDX file (<slug>.mdx) with frontmatter in its folder. Images the content uses are committed under that type's media folder.

Change the paths for a content type

Owners, Admins and Developers can open a content type's structure page (Posts, Pages or a Custom Content Type) and edit Repository Output:

  1. Content Folder — where that type's files are committed, for example src/content/blog or _posts.
  2. File Type — MDX (.mdx) or Markdown (.md).
  3. Media Folder — where its uploaded images are committed, for example public/images/blog.
  4. Media URL — the web path your site serves that media folder at. Leave it blank for folders under public/ or static/; Acrosite works it out.
  5. Choose Save Output Settings.

Folders must be relative, lowercase and must not start with a dot, and two content types cannot share one content folder. Keep media outside the content folder.

Important
Changing a folder does not move files that are already published. When you publish an item again, Acrosite writes it to the new folder and then removes the old file in a separate commit, but only if the old file is still exactly the file Acrosite published; otherwise the old file is kept and the item shows it as an old file you can remove. Items you do not publish again keep their old files. Images uploaded before the change keep their original folder. Redirects are not added for you.

Next steps

Frequently asked questions

Yes. Each content type has its own Repository Output settings for the content folder, the file type, the media folder and the media URL. Owners, Admins and Developers can change them.
They stay where they are until you publish the item again. Acrosite then writes it to the new folder and removes the old file in a separate commit, but only if the old file is still exactly the file Acrosite published. Items you do not publish again keep their old files; move or remove those yourself if you want.
By default media is committed under public/images/<type-key> and referenced as /images/<type-key>/.... Change the media folder and media URL per content type if your site keeps images elsewhere.