FrankenPHP 1.14.0 landed on 21 November 2026, two days after PHP 8.6 itself, and its headline change affects anyone who builds on the official images: PHP 8.6 is now the default. The latest Docker tag, the version-only tags (such as 1.14 or 1), the static binaries and the Windows builds all ship PHP 8.6.
If your Dockerfile says FROM dunglas/frankenphp, your next build will quietly move to a new PHP minor version. This guide explains what changed, how to pin your version, how to handle the missing mbstring and PECL in the PHP 8.6 images, and how to use the new file_server block in php_server.
All details come from the FrankenPHP v1.14.0 release notes and the FrankenPHP Docker docs.
What changed in FrankenPHP 1.14
PHP 8.6 by default
- Docker: images are built for PHP 8.6, and
latestplus version-only tags point to it. Images for older PHP versions stay available under theirphp8.xtags, for exampledunglas/frankenphp:1.14-php8.5. - Static binaries: built with PHP 8.6. Some extensions don’t have a release that supports PHP 8.6 yet (the notes list amqp, apcu, igbinary, imagick, lz4, memcached, msgpack, redis and xlswriter, among others), so the static builds use their development branches or pull requests that add support.
- Windows: builds use PHP 8.6 binaries compiled with Visual Studio 2026.
Upgrade note: no mbstring, no PECL
Like the official PHP images, the PHP 8.6 Docker images no longer include mbstring or PECL. You need to install the extensions you use with install-php-extensions. This one matters for Laravel apps in particular, because mbstring is on Laravel’s list of required PHP extensions.
A configurable file_server in php_server
The file_server subdirective of php_server now accepts a block with any file_server option except root (which stays on php_server). Serving pre-compressed assets becomes a one-liner.
Step 1: Decide whether to move to PHP 8.6 now
You have two safe options. What you should avoid is an unpinned FROM dunglas/frankenphp in production, because the PHP version can change under you.
Option A: stay on PHP 8.5 for now.
FROM dunglas/frankenphp:1.14-php8.5
You get FrankenPHP 1.14 with PHP 8.5, and can schedule the PHP upgrade separately.
Option B: move to PHP 8.6, and pin it explicitly.
FROM dunglas/frankenphp:1.14-php8.6
Tags follow the pattern dunglas/frankenphp:<frankenphp-version>-php<php-version>-<os>, where <os> is trixie, bookworm or alpine. The docs recommend the Debian variants. A fully pinned production tag might look like this (check Docker Hub for the exact tags available):
FROM dunglas/frankenphp:1.14-php8.6-trixie
Pinning both the FrankenPHP and PHP versions means you upgrade on purpose, in a pull request, with your test suite running.
Step 2: Add mbstring and your other extensions
The FrankenPHP images include the install-php-extensions script (from docker-php-extension-installer). On PHP 8.6 images, add mbstring to the list explicitly:
FROM dunglas/frankenphp:1.14-php8.6-trixie
RUN install-php-extensions \
mbstring \
pdo_mysql \
intl \
zip \
opcache
COPY . /app
Then check that the extension is actually loaded:
docker build -t my-app .
docker run --rm my-app php -m | grep -i mbstring
If grep prints nothing, the extension is missing. For a Laravel app, you can also run the framework’s own check inside the container:
docker run --rm my-app php artisan about
PECL extensions
Because PECL is no longer in the PHP 8.6 images, a line like RUN pecl install redis will fail. Use install-php-extensions instead:
RUN install-php-extensions redis
Be careful with extensions that don’t have a stable PHP 8.6 release yet (the release notes name redis, apcu, imagick, igbinary and memcached, among others). If your app depends on one of them, test the build carefully, or stay on the php8.5 tag until the extension ships a release that supports PHP 8.6.
Step 3: Test your app against PHP 8.6
Before switching production, run your test suite inside the new image. A quick way is to mount your code into a throwaway container:
docker run --rm -v "$PWD":/app -w /app \
dunglas/frankenphp:1.14-php8.6-trixie \
sh -c "install-php-extensions mbstring pdo_sqlite && php -v && php vendor/bin/phpunit"
Look for new deprecation notices in the output. PHP 8.6 adds new deprecations, so turn on E_ALL in your test environment and treat deprecations as warnings to fix before they become errors in a future version.
Also check your Composer constraints. If composer.json says "php": "~8.5.0" or similar, Composer will refuse to install on 8.6. A range such as "^8.3" allows it.
Step 4: Serve pre-compressed assets with the new file_server block
Before 1.14, serving pre-compressed files from php_server meant reordering directives or adding a handle block. Now you can configure the file server directly:
{
frankenphp
}
example.com {
root * /app/public
php_server {
file_server {
precompressed zstd br gzip
}
}
}
With precompressed zstd br gzip, Caddy’s file server looks for a pre-compressed sibling file (for example app.js.zst, app.js.br or app.js.gz) and serves the best one the browser accepts. Your build step just needs to produce those files:
# Example: pre-compress built assets
find public/build -type f \( -name '*.js' -o -name '*.css' \) \
-exec zstd -q -19 -k {} \; \
-exec brotli -q 11 -k {} \; \
-exec gzip -9 -k {} \;
Remember that root must stay on php_server (or the site), not inside the file_server block.
Step 5: Static binary users
If you run the standalone FrankenPHP binary rather than Docker, version 1.14 is now built with PHP 8.6. Check what you have after downloading:
./frankenphp version
./frankenphp php-cli -v
./frankenphp php-cli -m
The last command lists compiled-in extensions. Because some extensions in the static build come from development branches, run your app’s critical paths (sessions, caching, image processing) before rolling out.
Worker mode still works the same way
Nothing in 1.14 changes how worker mode is enabled. In Docker, you still set the FRANKENPHP_CONFIG environment variable:
ENV FRANKENPHP_CONFIG="worker ./public/index.php"
As with any PHP upgrade, restart workers after deploying so the new PHP version is used everywhere.
Upgrade checklist
- Replace unpinned
FROM dunglas/frankenphpwith an explicit tag. - Choose
-php8.5to wait, or-php8.6to move now. - On PHP 8.6 images, add
mbstringwithinstall-php-extensions. - Replace
pecl installlines withinstall-php-extensions. - Check extensions with
php -m, and run your full test suite. - Loosen tight PHP constraints in
composer.jsonif needed. - Optionally switch to
file_server { precompressed ... }for static assets.
Takeaway
FrankenPHP 1.14 is a small release with a big default change: PHP 8.6 everywhere. The safest move is to pin your tags today, either 1.14-php8.5 to wait or 1.14-php8.6 to move ahead. If you go to 8.6, remember that mbstring and PECL are no longer included in the images, so install your extensions explicitly and test before you deploy.
