---
type: concept
title: TYPO3 Caching
tags: ["typo3", "performance", "web-development", "cms", "caching"]
related: [typo3-backend, typo3-instructions, speaking-urls]
created: 2026-07-01
updated: 2026-07-01
sources: ["output/rz_uni_greifswald_de_dienste_webdienste_typo3_webseiten_typo3_anleitungen_grundl.md", "output/rz_uni_greifswald_de_dienste_webdienste_typo3_webseiten_typo3_anleitungen_video.md", "output/rz_uni_greifswald_de_dienste_webdienste_typo3_webseiten_typo3_faq.md"]
---

# TYPO3 Caching

**TYPO3 Caching** is a performance optimization system and mechanism that utilizes server-side caches to store pre-rendered versions of web pages. Its primary purposes are to significantly improve page load times for visitors and reduce the load on the web server.

## Server-side Content Caching

The server-side cache stores the representation of a page after its first creation. While this improves loading speeds, it can create a discrepancy or a "hurdle" for website editors because changes made in the [[typo3-backend]] may not be immediately visible on the live website (frontend).

### Impact on Editing
Specific impacts of content caching include:
- **General Content:** Changes made to content elements, page structures, or layouts may not appear immediately because the system continues to serve the cached version of the page rather than the most current data until the cache is cleared or expires.
- **Linked Data:** Changes involving linked data records may not appear immediately. This is particularly critical when using the "Insert Data Record" functionality, as the cached version of the page may still point to the old version of the central data record.

### Resolution and Overcoming the Cache
To resolve these discrepancies and ensure that updates are visible to the public, the TYPO3 cache must be cleared (flushed). This process forces the system to:
- Re-render the page with the most current data.
- Regenerate the page from the current database records rather than serving a stored snapshot.
- Ensure that the system generates a fresh version of the page reflecting the most recent changes.

#### Manual Cache Clearing
To force the frontend to display the most current content, editors can manually clear the cache for a specific page:
- **Location**: Navigate to the **Web > Page** module in the backend.
- **Action**: Click the **"lightning bolt" symbol** located in the top right of the content area.

Once cleared, the page will be rendered "live" upon the next frontend request.

## URL and Path Caching

Separate from content caching, TYPO3 caches the mapping of the page tree to "speaking URLs."

### Cache Types
- **Path Cache (Pfadcache)**: Stores the structural path of the page.
- **URL Cache (URL-Cache)**: Stores the specific URL mappings.

### Behavior and Resolution
These caches are responsible for the 30-day persistence of old URLs after a page has been moved or renamed. Clearing these caches in the "Sprechende URLs" module forces the system to use the current page tree structure immediately.