How to build a real-time chat application with Laravel?
Aug 04, 2025 pm 01:03 PMSet up Laravel and install dependencies including Laravel Sanctum and Laravel Echo. 2. Configure Pusher as the broadcast driver in .env and enable the BroadcastServiceProvider. 3. Create a Message model with a migration that includes user_id and message fields. 4. Implement authentication using Laravel’s built-in system. 5. Create a MessageSent event that implements ShouldBroadcast and uses a PresenceChannel for online user tracking. 6. Build a ChatController with methods to fetch and send messages, broadcasting the MessageSent event. 7. Design a frontend with Blade or Vue, integrate Laravel Echo, and listen for real-time events. 8. Compile assets, run the server, and test real-time messaging across multiple users. A real-time chat application in Laravel is successfully built using WebSockets via Pusher and Laravel Echo, enabling instant message broadcasting and dynamic UI updates.
Building a real-time chat application with Laravel is achievable by combining Laravel’s backend capabilities with real-time broadcasting using WebSockets. Here’s a practical guide to help you create a functional real-time chat app step by step.

1. Set Up Laravel and Laravel Echo Server
Start by creating a new Laravel project:
composer create-project laravel/laravel real-time-chat cd real-time-chat
Install Laravel Sanctum for API authentication (if using a SPA) or use Laravel’s built-in session auth:

composer require laravel/sanctum php artisan vendor:publish --provider="Laravel\Sanctum\SanctumServiceProvider" php artisan migrate
Install Laravel Echo and Pusher JS for client-side broadcasting:
npm install --save laravel-echo pusher-js
Note: Laravel Echo allows your JavaScript to listen for broadcasted events from Laravel.
2. Use Pusher for Real-Time Broadcasting
Laravel supports several broadcast drivers (Redis, Pusher, Soketi). Pusher is one of the easiest to set up for beginners.
Configure Broadcasting
In .env
, set:
BROADCAST_DRIVER=pusher PUSHER_APP_ID=your_app_id PUSHER_APP_KEY=your_app_key PUSHER_APP_SECRET=your_app_secret PUSHER_APP_CLUSTER=mt1
In config/broadcasting.php
, make sure Pusher settings are correct.
Enable Broadcasting
Uncomment this line in bootstrap/app.php
:
App\Providers\BroadcastServiceProvider::class,
3. Create the Chat Model and Migration
Generate a Message
model:
php artisan make:model Message -m
In the migration file:
Schema::create('messages', function (Blueprint $table) { $table->id(); $table->unsignedBigInteger('user_id'); $table->text('message'); $table->timestamps(); $table->foreign('user_id')->references('id')->on('users')->onDelete('cascade'); });
Run migration:
php artisan migrate
4. Set Up Authentication
Use Laravel’s built-in authentication:
php artisan make:auth
For Laravel 8 , you may need to use
laravel/ui
:
composer require laravel/ui php artisan ui vue --auth npm run dev
5. Create a Broadcast Event
Generate a new event:
php artisan make:event MessageSent
Edit app/Events/MessageSent.php
:
<?php namespace App\Events; use Illuminate\Broadcasting\Channel; use Illuminate\Broadcasting\InteractsWithSockets; use Illuminate\Broadcasting\PresenceChannel; use Illuminate\Broadcasting\PrivateChannel; use Illuminate\Contracts\Broadcasting\ShouldBroadcast; use Illuminate\Foundation\Events\Dispatchable; use Illuminate\Queue\SerializesModels; use App\Models\Message; class MessageSent implements ShouldBroadcast { use Dispatchable, InteractsWithSockets, SerializesModels; public $message; public function __construct(Message $message) { $this->message = $message; } public function broadcastOn() { return new PresenceChannel('chat'); } public function broadcastWith() { return [ 'id' => $this->message->id, 'user_id' => $this->message->user_id, 'message' => $this->message->message, 'created_at' => $this->message->created_at, ]; } }
Using
PresenceChannel
allows you to see who’s online. You can also usePrivateChannel
orChannel
depending on your needs.
6. Create the Chat Controller
php artisan make:controller ChatController
Add methods to fetch messages and send a message:
use App\Models\Message; use App\Events\MessageSent; public function fetchMessages() { return Message::with('user')->latest()->limit(100)->get()->reverse(); } public function sendMessage(Request $request) { $message = auth()->user()->messages()->create([ 'message' => $request->message ]); broadcast(new MessageSent($message))->toOthers(); return ['status' => 'Message Sent!']; }
Add the routes in routes/web.php
:
use App\Http\Controllers\ChatController; Route::middleware(['auth'])->group(function () { Route::get('/chat', function () { return view('chat'); }); Route::get('/messages', [ChatController::class, 'fetchMessages']); Route::post('/messages', [ChatController::class, 'sendMessage']); });
7. Build the Frontend (Blade or Vue)
Create a simple chat.blade.php
:
<div id="app"> <ul id="messages"> <li v-for="message in messages"> <strong>@{{ message.user.name }}:</strong> @{{ message.message }} </li> </ul> <input v-model="newMessage" @keyup.enter="sendMessage" placeholder="Type a message..." type="text" > </div> <script src="{{ asset('js/app.js') }}"></script>
Initialize Laravel Echo in resources/js/bootstrap.js
or app.js
:
import Echo from 'laravel-echo'; window.Pusher = require('pusher-js'); window.Echo = new Echo({ broadcaster: 'pusher', key: process.env.MIX_PUSHER_APP_KEY, cluster: process.env.MIX_PUSHER_APP_CLUSTER, forceTLS: true, authEndpoint: '/broadcasting/auth', });
Make sure to expose the Pusher key in .env
:
MIX_PUSHER_APP_KEY="${PUSHER_APP_KEY}" MIX_PUSHER_APP_CLUSTER="${PUSHER_APP_CLUSTER}"
Then in your Vue/JS logic:
const app = new Vue({ el: '#app', data: { messages: [], newMessage: '' }, mounted() { this.fetchMessages(); window.Echo.join('chat') .here((users) => { console.log('Users online:', users); }) .listen('MessageSent', (e) => { this.messages.push(e.message); }); }, methods: { fetchMessages() { axios.get('/messages').then(response => { this.messages = response.data; }); }, sendMessage() { axios.post('/messages', { message: this.newMessage }) .then(response => { this.newMessage = ''; }); } } });
8. Run and Test
Compile assets:
npm run dev
Start the Laravel development server:
php artisan serve
Open two browser windows, log in as different users, and test real-time messaging.
Final Notes
- For production, secure your broadcast routes with authentication.
- Consider rate limiting on message sending.
- Use
PresenceChannel
to show online users orPrivateChannel
for 1-on-1 chats. - For self-hosted WebSocket servers, consider using Soketi instead of Pusher.
Building a real-time chat app in Laravel isn’t overly complex once you understand the flow:
User sends message → Controller saves it → Event broadcasts it → Echo listens and updates UI.
With Laravel Echo and Pusher, most of the hard work is abstracted, letting you focus on UI and user experience.
Basically, that’s it — you’ve got a working real-time chat.
The above is the detailed content of How to build a real-time chat application with Laravel?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

There are three main ways to set environment variables in PHP: 1. Global configuration through php.ini; 2. Passed through a web server (such as SetEnv of Apache or fastcgi_param of Nginx); 3. Use putenv() function in PHP scripts. Among them, php.ini is suitable for global and infrequently changing configurations, web server configuration is suitable for scenarios that need to be isolated, and putenv() is suitable for temporary variables. Persistence policies include configuration files (such as php.ini or web server configuration), .env files are loaded with dotenv library, and dynamic injection of variables in CI/CD processes. Security management sensitive information should be avoided hard-coded, and it is recommended to use.en

Laravel's configuration cache improves performance by merging all configuration files into a single cache file. Enabling configuration cache in a production environment can reduce I/O operations and file parsing on each request, thereby speeding up configuration loading; 1. It should be enabled when the application is deployed, the configuration is stable and no frequent changes are required; 2. After enabling, modify the configuration, you need to re-run phpartisanconfig:cache to take effect; 3. Avoid using dynamic logic or closures that depend on runtime conditions in the configuration file; 4. When troubleshooting problems, you should first clear the cache, check the .env variables and re-cache.

When choosing a suitable PHP framework, you need to consider comprehensively according to project needs: Laravel is suitable for rapid development and provides EloquentORM and Blade template engines, which are convenient for database operation and dynamic form rendering; Symfony is more flexible and suitable for complex systems; CodeIgniter is lightweight and suitable for simple applications with high performance requirements. 2. To ensure the accuracy of AI models, we need to start with high-quality data training, reasonable selection of evaluation indicators (such as accuracy, recall, F1 value), regular performance evaluation and model tuning, and ensure code quality through unit testing and integration testing, while continuously monitoring the input data to prevent data drift. 3. Many measures are required to protect user privacy: encrypt and store sensitive data (such as AES

To enable PHP containers to support automatic construction, the core lies in configuring the continuous integration (CI) process. 1. Use Dockerfile to define the PHP environment, including basic image, extension installation, dependency management and permission settings; 2. Configure CI/CD tools such as GitLabCI, and define the build, test and deployment stages through the .gitlab-ci.yml file to achieve automatic construction, testing and deployment; 3. Integrate test frameworks such as PHPUnit to ensure that tests are automatically run after code changes; 4. Use automated deployment strategies such as Kubernetes to define deployment configuration through the deployment.yaml file; 5. Optimize Dockerfile and adopt multi-stage construction

Laravel's EloquentScopes is a tool that encapsulates common query logic, divided into local scope and global scope. 1. The local scope is defined with a method starting with scope and needs to be called explicitly, such as Post::published(); 2. The global scope is automatically applied to all queries, often used for soft deletion or multi-tenant systems, and the Scope interface needs to be implemented and registered in the model; 3. The scope can be equipped with parameters, such as filtering articles by year or month, and corresponding parameters are passed in when calling; 4. Pay attention to naming specifications, chain calls, temporary disabling and combination expansion when using to improve code clarity and reusability.

User permission management is the core mechanism for realizing product monetization in PHP development. It separates users, roles and permissions through a role-based access control (RBAC) model to achieve flexible permission allocation and management. The specific steps include: 1. Design three tables of users, roles, and permissions and two intermediate tables of user_roles and role_permissions; 2. Implement permission checking methods in the code such as $user->can('edit_post'); 3. Use cache to improve performance; 4. Use permission control to realize product function layering and differentiated services, thereby supporting membership system and pricing strategies; 5. Avoid the permission granularity is too coarse or too fine, and use "investment"

The core idea of PHP combining AI for video content analysis is to let PHP serve as the backend "glue", first upload video to cloud storage, and then call AI services (such as Google CloudVideoAI, etc.) for asynchronous analysis; 2. PHP parses the JSON results, extract people, objects, scenes, voice and other information to generate intelligent tags and store them in the database; 3. The advantage is to use PHP's mature web ecosystem to quickly integrate AI capabilities, which is suitable for projects with existing PHP systems to efficiently implement; 4. Common challenges include large file processing (directly transmitted to cloud storage with pre-signed URLs), asynchronous tasks (introducing message queues), cost control (on-demand analysis, budget monitoring) and result optimization (label standardization); 5. Smart tags significantly improve visual

To build a PHP content payment platform, it is necessary to build a user management, content management, payment and permission control system. First, establish a user authentication system and use JWT to achieve lightweight authentication; second, design the backend management interface and database fields to manage paid content; third, integrate Alipay or WeChat payment and ensure process security; fourth, control user access rights through session or cookies. Choosing the Laravel framework can improve development efficiency, use watermarks and user management to prevent content theft, optimize performance requires coordinated improvement of code, database, cache and server configuration, and clear policies must be formulated and malicious behaviors must be prevented.
