Edit Blade templates visually, straight into the .blade.php
Install one Composer package and every element in your own Blade views carries its file, line and column. Click it in the browser, change it, and PortBay splices the edit into that exact span of the .blade.php. Free in the app, no opt-in.
How do I edit Laravel Blade templates visually?
Editing a Blade template visually takes three things a browser cannot supply on its own: the rendered element has to carry a coordinate back to the .blade.php that produced it, the editor has to write to that file rather than to a database, and the change has to survive Blade's own compilation step. Most tools in this space solve none of the three — they store layout as JSON or CMS rows and render it, so what you edit is content, not your template. PortBay adds the coordinate with a Composer package, portbay/blade-stamper, which stamps each element with its file, line and column during the first Blade compilation pass. The edit is then spliced into that exact byte range, preserving your formatting and leaving no markers in your source. It is free, with no plan and no opt-in — Pro buys publishing to production — though it is absent from the open-source build.
Verified against the product, 2026-09-05.
A Laravel app, served and editable
PortBay runs your Laravel project at its own .test URL and dispatches board cards into it. The visual editor edits that same running project in your real browser — one live site, not a multi-frame design canvas.
Your first Blade edit
Five steps from a running Laravel app to a change committed in a .blade.php file. Every command runs as written.
- Install PortBay and add your Laravel project
- Turn the visual editor on
- Add the Blade stamper
- Open Edit in browser
- Switch to Edit, change something, save
Install PortBay and add your Laravel project
Homebrew installs the app and the bundled portbay CLI. Add the project folder and PortBay detects Laravel, serves it at its own .test hostname over trusted HTTPS, and starts PHP-FPM for you.
brew tap portbay-app/portbay && brew install --cask portbayTurn the visual editor on
It ships to everyone: no plan, no toggle, no cap on edits. What Pro buys is publishing to production, not editing. The open-source build does not include the editor at all — the entry point is not hidden there, it is not compiled in.
Open the project at its .test hostnameAdd the Blade stamper
Laravel renders on the server, so PortBay cannot inject stamping the way it does for Vite. This Composer package registers itself through Laravel's package auto-discovery — there is no config file to edit. Clear the view cache afterwards, because stamps are frozen in at Blade compile time.
composer require --dev portbay/blade-stamper && php artisan view:clearOpen Edit in browser
The project's Visual editing section has one button. It opens your normal browser at your normal .test URL with the edit bar docked at the top — your real routes, your real database, your real session. The bar boots in Preview mode, where the page is fully interactive and the bar does nothing.
https://myapp.testSwitch to Edit, change something, save
Double-click any text to type into the live page, or use the right rail for layout, spacing, typography and borders. Save asks you to disambiguate anything ambiguous first, then writes to source. A History panel keeps every change, so restoring is one click rather than a git stash.
The same change, without the editor
The hard part was never typing the new text. It was working out which of forty Blade files rendered the thing you clicked, and whether the row you edited is the row you meant.
With the stamper installed the element itself tells PortBay it came from home.blade.php line 37, column 5 — so a repeated row inside an @foreach resolves to the right one instead of the first match.
# which view rendered that heading?rg -n "Welcome aboard" resources/views/# resources/views/marketing/home.blade.php:37# resources/views/partials/hero.blade.php:12 <- or this one? # open it, edit it, then remember the compiled viewphp artisan view:clear # now do it again for the class change, and again for# the one inside the @foreach where every row looks the same
The pieces underneath
Visual editor
Click an element on your running site in your own browser and edit its text, classes and styles straight into the source file, across 21 stacks.
Explore →Local databases
Six engines, one wizard: isolated data dirs, dedicated ports, supervision, and connection vars injected into linked projects on start.
Explore →Asked before downloading
Don’t see your question answered here? The docs go deeper — every feature, flag and failure mode.
Read the docsYour files. PortBay splices the change into the exact byte range of the .blade.php that rendered the element, preserving the indentation and formatting around it. This is the difference from the page-builder packages that dominate this space: they store layout as JSON or database rows and render it, so the thing you edit is content in a CMS, not the template in your repo.
portbay/blade-stamper registers as the first Blade compilation pass, before Blade strips comments and rewrites component tags, and bakes a data-pb-loc attribute naming the file, line and column into each element it emits. It is a dev dependency, gated on the app environment, and it only touches views in your own view paths — a framework or package view comes back with no attribute at all. Nothing is written to your source files; the attribute exists only in the rendered HTML. Measured on served HTML against a zero-stamp control, it resolved 18 of 18 coordinates exactly on each of Laravel 11.55.1, 12.66.0 and 13.25.0.
For Laravel, yes: one dev dependency, composer require --dev portbay/blade-stamper, followed by php artisan view:clear. It ships on Packagist and registers through Laravel's package auto-discovery, so there is no service provider to add and no config file to edit. Vite projects need nothing installed at all, because PortBay launches those dev servers and can add stamping to its own launch.
Text, class and attribute edits still work — PortBay resolves them by searching your view files. What you lose is precision: structural edits (move, wrap, convert) are refused rather than guessed, style edits go to a PortBay override sheet instead of your templates, and repeated content can resolve to the wrong occurrence. PortBay says which mode it is in rather than degrading quietly.
Blade component tags themselves are deliberately not stamped: attributes on an <x-card> go to the component's attribute bag rather than the rendered output, so a coordinate placed there would be wrong. You edit the host elements inside your components, which are stamped normally. Views that ship inside Laravel or a vendor package are also skipped — a Laravel error page comes back with zero stamps.
No, and this is worth being plain about. It is free — the bar and the edits you make with it ship to everyone, with no plan and no opt-in. What Pro buys is publishing to production. It is still not compiled into the open-source build at all. Everything else on this page — the .test hostname, trusted HTTPS, PHP-FPM, the database, the task board — is in the free, open-source app.
Yes, in one specific way that is worth the setup on its own: renaming a design token rewrites every reference to it across the project in the same save, so the token definition and its uses never drift apart. Component extraction, which PortBay also offers, is a different matter — it is limited to Astro, JSX, Svelte and Vue, so it does not apply to Blade.
No. A project with a running tunnel is excluded from the visual editor entirely — the edit bar and its write-back endpoints are never routed onto public traffic. They are limited to local .test hosts, and the proxy behind them binds to loopback and rejects anything that did not arrive there, so a browser elsewhere on your network cannot reach them either.

Give your projects and your agents a real local home.
Download for macOSFree & open source · macOS 11+ on Apple Silicon · Pro from $10/mo