Eloquent Optimization: withExists and withCount Beyond N+1 | Mohamed Said [ ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MH.png) Mohamed Said Laravel Backend Engineer ](https://msaied.com) [ Home ](https://msaied.com) [ Projects ](https://msaied.com/projects) [ Articles ](https://msaied.com/articles) [ Certificates ](https://msaied.com/certificates) [ Contact ](https://msaied.com#contact-section) [ ](https://github.com/EG-Mohamed) [ Home ](https://msaied.com) [ Projects ](https://msaied.com/projects) [ Articles ](https://msaied.com/articles) [ Certificates ](https://msaied.com/certificates) [ Contact ](https://msaied.com#contact-section) [ home ](https://msaied.com) [ articles ](https://msaied.com/articles) Optimizing Eloquent Queries: Beyond N+1 with `withExists` and `withCount` On this page 1. [ Optimizing Eloquent Queries: Beyond N+1 with withExists and withCount ](#optimizing-eloquent-queries-beyond-n1-with-codewithexistscode-and-codewithcountcode) 2. [ The N+1 Problem Revisited ](#the-n1-problem-revisited) 3. [ Introducing withExists() ](#introducing-codewithexistscode) 4. [ Leveraging withCount() ](#leveraging-codewithcountcode) 5. [ Combining for Complex Scenarios ](#combining-for-complex-scenarios) 6. [ Takeaways: ](#takeaways) ![Optimizing Eloquent Queries: Beyond N+1 with `withExists` and `withCount`](https://cdn.msaied.com/160/89eca7b3d4a7f19692354a7621a64bb3.png) #Laravel #Eloquent #Performance #Optimization #N+1 #Database Optimizing Eloquent Queries: Beyond N+1 with `withExists` and `withCount` =========================================================================== 14 Jun 2026 4 min read ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said Table of contents 1. [ 01 Optimizing Eloquent Queries: Beyond N+1 with withExists and withCount ](#optimizing-eloquent-queries-beyond-n1-with-codewithexistscode-and-codewithcountcode) 2. [ 02 The N+1 Problem Revisited ](#the-n1-problem-revisited) 3. [ 03 Introducing withExists() ](#introducing-codewithexistscode) 4. [ 04 Leveraging withCount() ](#leveraging-codewithcountcode) 5. [ 05 Combining for Complex Scenarios ](#combining-for-complex-scenarios) 6. [ 06 Takeaways: ](#takeaways) Optimizing Eloquent Queries: Beyond N+1 with `withExists` and `withCount` ------------------------------------------------------------------------- N+1 query problems are a perennial concern in Laravel applications. The typical solution, `with()`, effectively eager loads related models, preventing a cascade of individual queries. However, `with()` is not always the most efficient tool, particularly when you only need to know *if* a relationship exists or *how many* related records there are, rather than the full related data itself. This article explores `withExists()` and `withCount()`, two powerful Eloquent methods that can drastically optimize query performance in specific, common scenarios. ### The N+1 Problem Revisited Consider a `Post` model with many `Comment` models. If you want to display a list of posts and indicate whether each post has *any* comments, a naive approach might look like this: ```php $posts = Post::all(); foreach ($posts as $post) { if ($post->comments->isNotEmpty()) { // Render 'Has Comments' badge } } ``` This code executes `Post::all()` (1 query) and then `SELECT * FROM comments WHERE post_id = ?` for *each* post (N queries), leading to N+1 queries. Eager loading with `with('comments')` would fetch all comments for all posts in a single additional query, but it still pulls potentially large datasets of comment bodies that aren't needed. ### Introducing `withExists()` When you only need to check for the *existence* of related records, `withExists()` is your ally. It adds a boolean attribute to each parent model, indicating whether the specified relationship has any associated records. This is achieved with a subquery, often more efficient than fetching all related data. Let's refactor the previous example: ```php $posts = Post::withExists('comments')->get(); foreach ($posts as $post) { if ($post->comments_exists) { // Render 'Has Comments' badge } } ``` This executes two queries: one for `posts` and one for the `comments_exists` subquery. The `comments_exists` attribute is automatically appended to each `Post` model. This is significantly more efficient than eager loading all comment data when only existence is required. You can also alias the existence column: ```php $posts = Post::withExists('comments as has_comments')->get(); // ... $post->has_comments ... ``` ### Leveraging `withCount()` Similarly, when you need to display the *number* of related records, `withCount()` is the optimal choice. It adds a `_count` attribute to the parent model, containing the count of related records, again via a subquery. Example: Displaying the number of comments for each post. ```php $posts = Post::withCount('comments')->get(); foreach ($posts as $post) { echo "Post: {$post->title}, Comments: {$post->comments_count}\n"; } ``` Like `withExists()`, this results in two efficient queries. You can also apply constraints to the count: ```php $posts = Post::withCount(['comments' => function ($query) { $query->where('approved', true); }])->get(); // $post->comments_count will now reflect only approved comments ``` And, of course, alias the count column: ```php $posts = Post::withCount('comments as total_comments')->get(); // ... $post->total_comments ... ``` ### Combining for Complex Scenarios You can combine `withExists()`, `withCount()`, and even `with()` for scenarios where you need both aggregate data and specific related models. ```php $posts = Post::withExists('comments as has_comments') ->withCount('likes') ->with('author') // Eager load the author relationship ->get(); foreach ($posts as $post) { echo "Post: {$post->title} (by {$post->author->name})\n"; echo " Has Comments: " . ($post->has_comments ? 'Yes' : 'No') . "\n"; echo " Likes: {$post->likes_count}\n"; } ``` This approach ensures that only the necessary data is fetched, leading to leaner queries and faster response times. Always profile your queries (e.g., with Laravel Debugbar or `DB::listen()`) to confirm the performance benefits in your specific context. ### Takeaways: - `withExists()` is ideal for checking the presence of related records without fetching their data. - `withCount()` efficiently retrieves the number of related records. - Both methods generate subqueries, often more performant than full eager loading when only existence or count is needed. - Alias the generated attributes for clarity and to avoid naming conflicts. - Combine these methods with `with()` when you need a mix of aggregate data and full related models. - Always profile your database interactions to validate optimization efforts. Found this useful? [ ](https://twitter.com/intent/tweet?url=https%3A%2F%2Fmsaied.com%2Farticles%2Foptimizing-eloquent-queries-beyond-n1-with-withexists-and-withcount&text=Optimizing+Eloquent+Queries%3A+Beyond+N%2B1+with+%60withExists%60+and+%60withCount%60) [ ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fmsaied.com%2Farticles%2Foptimizing-eloquent-queries-beyond-n1-with-withexists-and-withcount) Frequently Asked Questions ---------------------------- 2 questions Q01 When should I use `withExists()` instead of `with('relationship')->has('relationship')`? `withExists()` is generally more efficient. `with('relationship')->has('relationship')` would first eager load the relationship (potentially fetching all data) and then filter, whereas `withExists()` directly uses a subquery to check for existence without fetching the related data itself, leading to fewer columns and rows transferred from the database. Q02 Can I use `withCount()` with multiple relationships or custom conditions? Yes, `withCount()` accepts an array of relationships, and each can have a closure to apply custom query constraints. For example: `Post::withCount(['comments', 'likes' => fn ($q) => $q->where('active', true)])->get();` Continue reading More Articles --------------- [ View all ](https://msaied.com/articles) [ ![Eloquent Custom Casts: Encapsulating Value Objects Without the Bloat](https://cdn.msaied.com/174/2c75896ee4182bb2f66e2c93bed18796.png) laravel eloquent ddd ### Eloquent Custom Casts: Encapsulating Value Objects Without the Bloat Custom Eloquent casts let you bind rich value objects directly to model attributes. This article shows how to... ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said 14 Jun 2026 1 min read Read ](https://msaied.com/articles/eloquent-custom-casts-encapsulating-value-objects-without-the-bloat) [ ![Filament v4 Schema-Based Forms: Unified Schema API in Practice](https://cdn.msaied.com/173/6e0d9faa9137cb296e37831c3645e7ba.png) filament laravel filament-v4 ### Filament v4 Schema-Based Forms: Unified Schema API in Practice Filament v4 replaces scattered form/infolist definitions with a single Schema API. This post walks through rea... ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said 14 Jun 2026 3 min read Read ](https://msaied.com/articles/filament-v4-schema-based-forms-unified-schema-api-in-practice) [ ![The Pipeline Pattern in Laravel: Building Custom Pipelines Beyond Middleware](https://cdn.msaied.com/172/a5dea5e84a6eab22d5d7a76869aaecb4.png) laravel design-patterns pipeline ### The Pipeline Pattern in Laravel: Building Custom Pipelines Beyond Middleware Laravel's Pipeline class is far more than the engine behind HTTP middleware. Learn how to compose reusable, te... ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said 14 Jun 2026 3 min read Read ](https://msaied.com/articles/the-pipeline-pattern-in-laravel-building-custom-pipelines-beyond-middleware) [ ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MH.png) Mohamed Said Laravel Backend Engineer ](https://msaied.com)Senior Backend Engineer specializing in Laravel, scalable SaaS platforms, APIs, and cloud infrastructure. I build secure, high-performance web applications that help businesses grow. Explore - [Home](https://msaied.com) - [Projects](https://msaied.com/projects) - [Articles](https://msaied.com/articles) - [Certificates](https://msaied.com/certificates) - [Contact](https://msaied.com#contact-section) Connect - [ hello@msaied.com ](mailto:hello@msaied.com) - [ +20 109 461 9204 ](tel:+201094619204) © 2026 Mohamed Said. All rights reserved. [ ](https://github.com/EG-Mohamed) [ ](https://www.linkedin.com/in/msaiedm/) [ ](https://wa.me/201094619204) [ ](mailto:hello@msaied.com) [ ](https://drive.google.com/file/u/0/d/1MF20IPRJyzfy32mhEutjL5EpSls0w2Q8/view)