FrankenPHP includes a built-in hot reload feature designed to vastly improve the developer experience.

This feature provides a workflow similar to Hot Module Replacement (HMR) found in modern JavaScript tooling (like Vite or webpack). Instead of manually refreshing the browser after every file change (PHP code, templates, JavaScript and CSS files…), FrankenPHP updates the content in real-time.
Hot Reload natively works with WordPress, Laravel, Symfony, and any other PHP application or framework.
When enabled, FrankenPHP watches your current working directory for filesystem changes. When a file is modified, it pushes a Mercure update to the browser.
Depending on your setup, the browser will either:
To enable hot reloading, enable Mercure, then add the hot_reload sub-directive to the php_server directive in your Caddyfile.
Warning
This feature is intended for development environments only. Do not enable
hot_reloadin production, as watching the filesystem incurs performance overhead and exposes internal endpoints.
localhost
mercure {
anonymous
}
root public/
php_server {
hot_reload
}
By default, FrankenPHP will watch all files in the current working directory matching this glob pattern: ./**/*.{css,env,gif,htm,html,jpg,jpeg,js,mjs,php,png,svg,twig,webp,xml,yaml,yml}
It’s possible to explicitly set the files to watch using the glob syntax:
localhost
mercure {
anonymous
}
root public/
php_server {
hot_reload src/**/*{.php,.js} config/**/*.yaml
}
Use the long form to specify the Mercure topic to use as well as which directories or files to watch by providing paths to the hot_reload option:
localhost
mercure {
anonymous
}
root public/
php_server {
hot_reload {
topic hot-reload-topic
watch src/**/*.php
watch assets/**/*.{ts,json}
watch templates/
watch public/css/
}
}
While the server detects changes, the browser needs to subscribe to these events to update the page.
FrankenPHP exposes the Mercure Hub URL to use for subscribing to file changes via the $_SERVER['FRANKENPHP_HOT_RELOAD'] environment variable.
A convenience JavaScript library, frankenphp-hot-reload, is also available to handle the client-side logic. To use it, add the following to your main layout:
<!DOCTYPE html>
<title>FrankenPHP Hot Reload</title>
<?php if (isset($_SERVER['FRANKENPHP_HOT_RELOAD'])): ?>
<meta name="frankenphp-hot-reload:url" content="<?=$_SERVER['FRANKENPHP_HOT_RELOAD']?>">
<script src="https://cdn.jsdelivr.net/npm/idiomorph"></script>
<script src="https://cdn.jsdelivr.net/npm/frankenphp-hot-reload/+esm" type="module"></script>
<?php endif ?>
The library will automatically subscribe to the Mercure hub, fetch the current URL in the background when a file change is detected and morph the DOM. It is available as a npm package and on GitHub.
Alternatively, you can implement your own client-side logic by subscribing directly to the Mercure hub using the EventSource native JavaScript class.
If you are running your application in Worker Mode, your application script remains in memory. This means changes to your PHP code will not be reflected immediately, even if the browser reloads.
For the best developer experience, you should combine hot_reload with the watch sub-directive in the worker directive.
hot_reload: refreshes the browser when files changeworker.watch: restarts the worker when files changelocalhost
mercure {
anonymous
}
root public/
php_server {
hot_reload
worker {
file /path/to/my_worker.php
watch
}
}
e-dant/watcher library under the hood (we contributed the Go binding).watch is enabled in the worker config, the PHP worker is restarted to load the new code.window.location.reload() is called to refresh the page.