---
title: "Breaking: #78222 - Extension autoload information is now in typo3conf/autoload"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:breaking-78222"
source: "Changelog/8.4/Breaking-78222-ExtensionAutoloadInformationIsNowInTypo3confautoload.rst"
typo3-version: "8.4"
typo3-major: 8
type: "breaking"
issue: 78222
forge: "https://forge.typo3.org/issues/78222"
tags: ["PHP-API"]
rendered: "2026-09-20T18:31:11+00:00"
---

# Breaking: #78222 - Extension autoload information is now in typo3conf/autoload {#breaking-78222}

See [forge#78222](https://forge.typo3.org/issues/78222)

## Description {#description}

To make clear that autoload information is not a cache,
the files have been moved from `typo3temp` to `typo3conf`.

## Impact {#impact}

TYPO3 deployments which do not take advantage of composer, might need some adaption
to also include the new location in `typo3conf` in the list of to be synced files.

## Affected Installations {#affected-installations}

TYPO3 installation in non composer mode.

## Migration {#migration}

Class loading information can be re-dumped by

-   Activating or deactivating an extension
-   Running the dump command from the command line
-   In install tool (important actions)

The autoload files should never be deleted, but always only be re-dumped.