How Laravel Route Caching Works

In Laravel, a route tells Laravel which code should handle an HTTP request, such as GET /profile. As the application starts, Laravel normally reads its route files and registers each route. Route caching saves those registered routes in a prepared table, so Laravel can load the table on later requests instead of registering every route again.

This saves Laravel work, especially in applications with many routes. If you edit a route file, Laravel keeps using the saved route table until you clear or rebuild the cache, so the change does not take effect right away.

What Laravel saves

Run php artisan route:cache to generate the route cache. Laravel prepares the registered routes and stores them in a format it can load later. Laravel calls the set of registered routes held in memory a route collection. When Laravel builds the cache, it turns that collection into compiled route data that it uses to match incoming requests, as shown in its RouteCollection implementation.

Here, “compiled” means Laravel has prepared route information for its matcher. It does not mean Laravel compiled controller code. When the cache exists, Laravel’s route-loading code skips loading the route files used to build that cached route table. The service provider code shows that behavior.

Why route caching can speed up startup

Without a route cache, Laravel registers routes from the application’s route files during startup. With the cache, Laravel loads the prepared route data instead, so it does less work to register routes. Laravel’s deployment documentation recommends route caching especially for large applications with hundreds of routes.

The improvement depends on the application. Laravel does not promise a fixed reduction in request time, and route caching does not cache controller responses or database results. It targets route registration and uses compiled data for route matching; the rest of the request, including middleware and controller execution, still runs.

Why route edits do not appear

The route cache stores the route definitions Laravel used when it generated the cache. If you change a route file afterward, the cache still describes the earlier route table. Laravel keeps loading that saved table, so a new or edited route does not take effect until you update the cache. Laravel’s routing documentation directs developers to generate a fresh cache after adding routes.

After changing routes, clear and rebuild the cache:

php artisan route:clear
php artisan route:cache

Run these commands after updating the route files, commonly as part of deployment. Clearing removes the old route table; rebuilding creates a new one from the current definitions.

What I'm building

Delegate tasks. Get software.

Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.

Take a look at vroni.com