Laravel Default Database Tables Explained in Detail

Setting up a brand-new Laravel project automatically generates between 7 and 8 database tables depending on the installed packages. The core tables include users, password_resets, failed_jobs, and personal_access_tokens. None of these tables are set in stone, meaning developers have the flexibility to rename, extend, or replace any of them based on project requirements.

Only a subset of these tables—specifically users, password_resets, and failed_jobs—are generated when running standard migrations. Tables such as sessions, cache, jobs, and batches require running dedicated Artisan commands before they appear in your database schema.

Stock photo for illustration only, not from the actual event

Here is a breakdown of the default Laravel database tables:

• users: Stores core user account information.
• password_resets / password_reset_tokens: Manages password reset tokens (renamed in Laravel 8 and newer versions).
• failed_jobs: Used for debugging failed queue tasks, featuring an exception column with full stack traces.
• personal_access_tokens: Created by Laravel Sanctum to handle API token authentication.
• sessions: Generated via php artisan session:table to store HTTP session data in the database instead of files.
• cache: Generated via php artisan cache:table to store key-value cache entries.
• jobs: Generated via php artisan queue:table to hold pending queue jobs.
• batches: Generated via php artisan queue:batches-table to track parallel job processing progress.

Furthermore, Laravel natively supports Redis for handling sessions, cache, and queues out of the box. Simply updating your .env driver to redis eliminates the need for these database tables altogether. To visualize your schema, tools like dbdiagram.io allow you to paste your connection string and generate a visual diagram of all your Laravel tables instantly.

Source: Dev.to