A visual editor for Laravel’s Blade views.
midcode opens a Laravel app on a live canvas and edits its Blade views: text, classes, attributes, new elements and their order, written into the .blade.php file. Your {{ }} output, @directives and PHP blocks are left exactly as written. midcode serves the app with PHP’s own server and tags the views as Blade compiles them, without changing a file in the project.
Free for 3 days, no card. Then one payment, yours for life.
v1.1.2Today’s version shows a Laravel app that uses Vite at its APP_URL, to check every breakpoint and leave comments. Editing Blade views ships with the next release.
- Status
- Blade editing in the next release
- Edits
- .blade.php views
- Needs
- PHP on your Mac
- Tried with
- Laravel 13, PHP 8.5
01/What you can do
What midcode does with Laravel.
Click to code
Select any element and read where it’s written: the file and the line. Copy that reference into your agent, or open the file on that line.
Edit text in place
Double-click a heading, a button or a paragraph and type. The new text replaces the old one in the file, and nothing else in it changes.
Every breakpoint at once
Your site runs live at Desktop, Tablet and Phone, side by side, at full page height. A style set on one breakpoint is written for that breakpoint.
Routes as pages
The GET routes in routes/web.php are the pages you move between from the top bar.
Swap images and video
Drop a new image on an element, or paste one with ⌘V. midcode copies the file into your project and rewrites the reference.
Drag to reorder
Move an element before, after or inside another one, on the canvas or in Layers. The markup moves in the file, with the comment above it.
02/How it works
Three steps. No new workflow.
Step 1: Open the project folder
midcode serves the app the way artisan serve does, with one file loaded first that has Blade hand each view over to be tagged. Compiled views go to a folder of midcode’s, not to storage/.
Step 2: Edit on the canvas
Each change is written into the view. The page reloads when anything in resources/ changes.
Step 3: Publish
Review what changed, then commit and push in one step.
03/Good to know
The honest part.
What it doesn’t do
- Text that PHP prints ({{ $title }}) is edited where the value is written, not on the canvas.
- Blade components (<x-card>) and Livewire components are shown, and edited in their own view: the instance itself isn’t selectable yet.
- Not tried yet with Herd, Livewire or Inertia.
Coming next
- The database behind the app: its tables and SQL, read from the DB_* values in your .env.
04/FAQ
Laravel questions. Short answers.
No. The tags are added while Blade compiles, by a file PHP loads before your app, and the compiled views are kept outside the project. Nothing in vendor/, storage/ or your views is modified until you edit something.
Yes. With Vite, midcode runs it beside the app. With Tailwind CSS 4 the panel writes your own utilities. Without Tailwind it writes its own prefixed ones.
The app still opens if something is already serving it at its APP_URL (Herd, Valet): you can check breakpoints and comment. Editing Blade needs php on your PATH.
05/Goes with
The rest of your stack.
Open your Laravel project.
Download midcode, point it at your project folder and click something. Three days free, no card, nothing added to your code.