Core Forms 4.8
Every Core Forms stylesheet and script is served minified, cutting the front-end CSS and JavaScript payload by about 23 percent, with readable sources still in the package. Page-level form detection now covers reusable blocks, widgets and template parts. Released August 29, 2026.
Core Forms 4.8 is out as of August 29, 2026. It is a small release with one subject: what the plugin sends to the browser. Every first-party stylesheet and script is now served minified, which takes about 23 percent off the CSS and JavaScript payload across the library, and the form stylesheet alone drops by 48 percent. Nothing about how a form looks or behaves changed.
This post covers the release in full. There is nothing to reconfigure and no migration runs. If you debug against the plugin’s source, one constant and one filter give you the readable files back, and both are named below.
The update is a click away under Dashboard, then Updates. The changelog has the raw list, and the support page is there for anything that does not behave as described.
What’s New in Core Forms 4.8
Two things changed, and the second one is the more interesting of the two if your theme puts forms anywhere other than inside a post.
Minified Assets
All first-party CSS and JavaScript is served minified, on the front end and in the admin. The payload across the library is about 23 percent smaller, roughly 160 KB in total, and the three files a visitor is most likely to receive shrink the most:
forms.cssdrops 48 percent.forms.jsdrops 48 percent.smart-forms.jsdrops 52 percent.
The readable sources still ship in the package. Defining SCRIPT_DEBUG in wp-config.php serves them instead of the minified files, and the new cf_use_minified_assets filter does the same from code, so a debugging session or a staging site can read the plugin’s own source without swapping the build. A new Core_Forms\Assets class resolves each asset path to the file that should be served, with that filter as the escape hatch.
Assets that arrive already minified, the webpack admin bundle and the vendored Prism, are served as they are rather than duplicated. On the build side, npm run build:assets regenerates the minified files and build.sh fails the build when they are stale, so a release cannot ship a minified file older than its source.
Form Detection Beyond Post Content
Since 4.3.2 the plugin has loaded form assets only on pages that render a form. That detection read post content. A form placed in a reusable block, a widget area or a block-theme template part was found late, after the page had started painting, so its stylesheets fell back to the footer and the form flashed unstyled for a moment.
Page-level detection now inspects reusable blocks, widget areas and template parts too, and a form in any of those gets its stylesheets in <head>. Polls, the customer licensing portal and the admin screens each load their own assets only where they are used.
The Limits
Minification changes bytes, not requests. A page with a form still loads the form stylesheet and script; each one is smaller, but the count is the same.
Third-party code that was already minified is unchanged. The 23 percent is Core Forms’ own files.
A full-page cache or a CDN keeps serving the old files until it refreshes or the version string changes. The saving shows on a fresh render, so a page cached before the update looks the same until it is purged.
Docs and Links
- Core Forms 4.8 in the changelog.
- Stop stylesheet bloat, on why a forms plugin should load nothing on pages without forms.
- Embedding forms, which covers blocks, shortcodes, widgets and template parts.
- The previous release, Core Forms 4.7.
Final Remarks
If you have updated, your visitors download less for the same form, and a form in a header, footer or sidebar gets its styles before the first paint instead of after it. The idea to keep is the one this whole line of releases has been working toward: a forms plugin should be invisible on pages without forms and light on pages with them.
After updating, a few things are worth a look. View the source of one page that has a form outside the post content and confirm the Core Forms stylesheet sits in the head. Make sure SCRIPT_DEBUG is off in production, because with it on you are serving the readable files to everyone. And if a page cache or CDN sits in front of the site, purge it once so the new version string reaches visitors.
The embedding guide covers each placement, and the support page is there if a form still paints unstyled somewhere.
That is the whole release. I hope the saving shows up somewhere you can measure it.