ActiveRecord where vs find_by — Which to Use When

Most Rails developers use where and find_by interchangeably early on. That works until it doesn’t.

The Core Difference

find_by executes immediately and returns one record (or nil):

User.find_by(email: "raza@example.com")
# SELECT * FROM users WHERE email = 'raza@example.com' LIMIT 1
# => #<User ...> or nil

where returns an ActiveRecord::Relation — it doesn’t hit the database until you call something that forces execution:

User.where(email: "raza@example.com")
# => ActiveRecord::Relation  (not executed yet)

User.where(email: "raza@example.com").first
# SELECT * FROM users WHERE email = 'raza@example.com' LIMIT 1

When find_by Is the Right Call

Use find_by when:

• You expect zero or one record
• You want nil back if nothing matches (not an exception)
• You are done chaining after this call

account = Account.find_by(subdomain: params[:subdomain])
return render :not_found unless account

find_by(id: x) is safer than find(x) — returns nil instead of raising ActiveRecord::RecordNotFound. Use find only when absence is a bug.

When where Is the Right Call

Use where when:

• You expect multiple records
• You need to chain more conditions, scopes, or ordering
• You are building a query progressively

User.where(role: "admin").where("created_at > ?", 1.week.ago).order(:name)

where composes cleanly with scopes:

User.active.where(plan: "pro").limit(20)

find_by cannot chain. The moment you need another condition or ordering, use where.

The Trap: find_by with Multiple Conditions

User.find_by(role: "admin", active: true)
# Returns ONE admin user — whichever the DB returns first

If you meant all admin users, this silently gives you one. Use where.

What About find?

find raises ActiveRecord::RecordNotFound if the record is missing:

User.find(params[:id])
# Raises if not found — Rails handles the 404 for you

Use find in controller show actions. Use find_by when you will handle nil yourself.

Performance

No difference in the query itself. Both generate the same SQL for single-record lookups. find_by adds LIMIT 1 automatically.

Quick Reference

The Rule

• One record, done: find_by
• One record, absence is a bug: find
• Multiple records or chaining: where

Check every find_by in your codebase where you immediately call .first or .last on the result. That is where(…).first and should be written explicitly. Learn more about rails in our guide: Does ActiveRecord find_by Return nil? (Guide 2026).