Need help with laravel-debugbar?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

12.6K Stars 1.2K Forks MIT License 878 Commits 43 Opened issues


Laravel Debugbar (Integrates PHP Debug Bar)

Services available


Need anything else?

Contributors list

Laravel Debugbar

Unit Tests Packagist License Latest Stable Version Total Downloads

This is a package to integrate PHP Debug Bar with Laravel. It includes a ServiceProvider to register the debugbar and attach it to the output. You can publish assets and configure it through Laravel. It bootstraps some Collectors to work with Laravel and implements a couple custom DataCollectors, specific for Laravel. It is configured to display Redirects and (jQuery) Ajax Requests. (Shown in a dropdown) Read the documentation for more configuration options.

Debugbar 3.3 Screenshot

Note: Use the DebugBar only in development. It can slow the application down (because it has to gather data). So when experiencing slowness, try disabling some of the collectors.

This package includes some custom collectors: - QueryCollector: Show all queries, including binding + timing - RouteCollector: Show information about the current Route. - ViewCollector: Show the currently loaded views. (Optionally: display the shared data) - EventsCollector: Show all events - LaravelCollector: Show the Laravel version and Environment. (disabled by default) - SymfonyRequestCollector: replaces the RequestCollector with more information about the request/response - LogsCollector: Show the latest log entries from the storage logs. (disabled by default) - FilesCollector: Show the files that are included/required by PHP. (disabled by default) - ConfigCollector: Display the values from the config files. (disabled by default) - CacheCollector: Display all cache events. (disabled by default)

Bootstraps the following collectors for Laravel: - LogCollector: Show all Log messages - SwiftMailCollector and SwiftLogCollector for Mail

And the default collectors: - PhpInfoCollector - MessagesCollector - TimeDataCollector (With Booting and Application timing) - MemoryCollector - ExceptionsCollector

It also provides a Facade interface for easy logging Messages, Exceptions and Time


Require this package with composer. It is recommended to only require the package for development.

composer require barryvdh/laravel-debugbar --dev

Laravel uses Package Auto-Discovery, so doesn't require you to manually add the ServiceProvider.

The Debugbar will be enabled when


If you use a catch-all/fallback route, make sure you load the Debugbar ServiceProvider before your own App ServiceProviders.

Laravel without auto-discovery:

If you don't use auto-discovery, add the ServiceProvider to the providers array in config/app.php


If you want to use the facade to log messages, add this to your facades in app.php:

'Debugbar' => Barryvdh\Debugbar\Facade::class,

The profiler is enabled by default, if you have APPDEBUG=true. You can override that in the config (

) or by setting `DEBUGBARENABLED

in your
. See more options in
You can also set in your config if you want to include/exclude the vendor files also (FontAwesome, Highlight.js and jQuery). If you already use them in your site, set it to false.
You can also only display the js or css vendors, by setting it to 'js' or 'css'. (Highlight.js requires both css + js, so set to
true` for syntax highlighting)

Copy the package config to your local config with the publish command:

php artisan vendor:publish --provider="Barryvdh\Debugbar\ServiceProvider"


For Lumen, register a different Provider in

if (env('APP_DEBUG')) {

To change the configuration, copy the file to your config folder and enable it:



You can now add messages using the Facade (when added), using the PSR-3 levels (debug, info, notice, warning, error, critical, alert, emergency):

Debugbar::warning('Watch out…');
Debugbar::addMessage('Another message', 'mylabel');

And start/stop timing:

Debugbar::startMeasure('render','Time for rendering');
Debugbar::addMeasure('now', LARAVEL_START, microtime(true));
Debugbar::measure('My long operation', function() {
    // Do something…

Or log exceptions:

try {
    throw new Exception('foobar');
} catch (Exception $e) {

There are also helper functions available for the most common calls:

// All arguments will be dumped as a debug message
debug($var1, $someString, $intValue, $object);

// $collection->debug() will return the collection and dump it as a debug message. Like $collection->dump() collect([$var1, $someString])->debug();

start_measure('render','Time for rendering'); stop_measure('render'); add_measure('now', LARAVEL_START, microtime(true)); measure('My long operation', function() { // Do something… });

If you want you can add your own DataCollectors, through the Container or the Facade:

Debugbar::addCollector(new DebugBar\DataCollector\MessagesCollector('my_messages'));
//Or via the App container:
$debugbar = App::make('debugbar');
$debugbar->addCollector(new DebugBar\DataCollector\MessagesCollector('my_messages'));

By default, the Debugbar is injected just before

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.