by spatie

Painless html generation

468 Stars 68 Forks Last release: about 2 months ago (2.27.0) MIT License 328 Commits 62 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

Painless html generation

Latest Version on Packagist MIT Licensed Test Status Code Style Status Total Downloads

This package helps you generate HTML using a clean, simple and easy to read API. All elements can be dynamically generated and put together. The HTML builder helps you generate dynamically assigned form elements based on your selected model, the session or a default value.

Support us

Learn how to create a package like this one, by watching our premium video course:

Laravel Package training

We invest a lot of resources into creating best in class open source packages. You can support us by buying one of our paid products.

We highly appreciate you sending us a postcard from your hometown, mentioning which of our package(s) you are using. You'll find our address on our contact page. We publish all received postcards on our virtual postcard wall.


You're free to use this package (it's MIT-licensed), but if it makes it to your production environment we highly appreciate you sending us a postcard from your hometown, mentioning which of our package(s) you are using.

Our address is: Spatie, Kruikstraat 22, 2018 Antwerp, Belgium.

All postcards are published on our website.


You can install the package via composer:

composer require spatie/laravel-html

Next, you must install the service provider:

// config/app.php
'providers' => [

And optionally register an alias for the facade.

// config/app.php
'aliases' => [
    'Html' => Spatie\Html\Facades\Html::class,



Elements—classes under the

namespace—are generally created via a
builder instance.
html()->span()->text('Hello world!');

Element attributes and contents are modified via with fluent methods which return a new instance. This means element instances are immutable.

$icon = html()->span()->class('fa');

$icon->class('fa-eye'); // '' $icon->class('fa-eye-slash'); // ''

Element classes don't have any knowledge of the outside world. Any coupling to other concepts, like requests and sessions, should happen in the builder class, not on the element classes.

By convention, we assume that builder methods will modify values to our advantage (like pulling old values from the session on a failed form request), and element methods will be deterministic.

// This will try to resolve an initial value, and fall back to '[email protected]'
$email = html()->email('email', '[email protected]');

// This will always have '[email protected]' as it's value $email = html()->email('email')->value('[email protected]');


From v1 to v2

Version 2 was created because the typehints in version 1 was holding the package back in some cases (like multiple select which requires an array of values instead of a string which was assumed).

Luckily, bumping the version number in

and running
composer update
should be non-breaking. Here are some caveats to look out for:
  • The package now ships with a
    function by default, which returns an instance of the
    builder class. If you've defined your own method, you'll need to remove it.
  • Various type hints have been removed throughout the package, if you've extended a class to override its methods, you'll need to update them accordingly (everything still behaves the same!)


Please see CHANGELOG for more information what has changed recently.


$ composer test


Please see CONTRIBUTING for details.


If you discover any security related issues, please email [email protected] instead of using the issue tracker.


About Spatie

Spatie is a webdesign agency based in Antwerp, Belgium. You'll find an overview of all our open source projects on our website.


The MIT License (MIT). Please see License File for more information.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.