Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

thewebartisan7's avatar

Laravel official form builder

Seem that Laravel 5.x don't have any form builder. In docs I can find only for 4.x version. Was this removed? Which package you suggest to use?

Thanks

0 likes
8 replies
tykus's avatar
tykus
Best Answer
Level 104

It was removed from core and maintained by Laravel Collective instead.

Do you really need a Form Builder though?

1 like
thewebartisan7's avatar

Thank you both!

Not sure who reply before, but both have right, which mark correct?

I understand that is not required to have a form builder, but it can be really a time saving in certain project.

For example I see that the package which you refer allow to bind from model, or to create components, so this is my form:

                {{ Form::model($permission, ['route' => ['permissions.update', $permission->id]]) }}
                    {{ Form::bsText('name') }}
                    {{ Form::bsText('guard_name') }}
                    {{ Form::bsSubmit('Create') }}
                {{ Form::close() }}

The model $permission will populate the value auto-magically in the form by matching the name of input.

And one of the components that I can reuse using {{ Form::bsText('name') }}

<div class="form-group">
    {{ Form::label($name, null, ['class' => 'control-label']) }}
    {{ Form::text($name, $value, array_merge(['class' => 'form-control'], $attributes)) }}
</div>

Much cleaner and time-saving in my opinion.

But I agree that in small project is not really required.

Tray2's avatar

I missed it to when it was removed but now it feels more like I'm in control over my form and it's a bit faster not to have blade convert it to html every time.

thewebartisan7's avatar

I don't think that it take much difference if blade need to convert it; as I understand it use similar like blade components. Also this is basically for admin area, where it should not make too much difference bit faster or slower rendering time.

tykus's avatar

it's a bit faster not to have blade convert it to html every time

Blade gets compiled and cached the first time a view is used, not every time

Snapey's avatar

You will find that after a while you start to spend more and more time trying to get the Form classes to do what you want and in the event you will realise that they are a crap idea.

2 likes
thewebartisan7's avatar

You will find that after a while you start to spend more and more time trying to get the Form classes to do what you want and in the event you will realise that they are a crap idea.

I hear you, and I have already experience what you are saying. This can happen if you start abstract too much things. But if you keep it simple as possible, it should not be a problem. And when happen, you can always make a normal form using html directly.

Please or to participate in this conversation.