Does ActiveRecord find_by Return nil? (Complete Guide 2026)

Quick Answer

Yes, ActiveRecord’s find_by returns nil if no record is found. This is different from find, which raises ActiveRecord::RecordNotFound.

# Returns nil if not found
user = User.find_by(email: 'missing@example.com')
# => nil

# Raises exception if not found
user = User.find(999999)
# => ActiveRecord::RecordNotFound

When find_by Returns nil

The find_by method returns nil in these situations:

1. No record matches the given conditions
2. The table is empty
3. The attribute value doesn’t exist in any record

find vs find_by Comparison

Safe nil Handling Patterns

1. Safe Navigation Operator

user = User.find_by(email: params[:email])
user&.update(last_login: Time.current)

2. Presence Check

if user = User.find_by(email: params[:email])
  user.send_welcome_email
else
  flash[:error] = "User not found"
end

3. find_or_create_by

user = User.find_or_create_by(email: params[:email]) do |u|
  u.name = params[:name]
end

4. find_or_initialize_by

user = User.find_or_initialize_by(email: params[:email])
user.new_record? # => true if not found

5. Default Value with ||

user = User.find_by(email: params[:email]) || User.new

Production Best Practices

1. Always handle nil: Never assume find_by will return a record
2. Use find for IDs: When searching by ID and record must exist
3. Use find_by for attributes: When searching by email, username, etc.
4. Log unexpected nils: Track when expected records aren’t found We’ve covered SQL to ActiveRecord in depth here: ActiveRecord to Raw SQL—When ORM Costs 80% Performance in Production.

Common Mistakes

❌ Don’t do this:

user = User.find_by(email: params[:email])
user.name # NoMethodError if nil!

✅ Do this instead:

user = User.find_by(email: params[:email])
user&.name || "Guest"

Related Methods

• find: Search by ID, raises if not found
• find_by!: Like find_by but raises if not found
• where(...).first: Similar to find_by but less efficient
• exists?: Check if record exists without loading it

Summary

• find_by always returns nil when no record matches
• Use safe navigation (&.) or presence checks to handle nil
• Choose find when record must exist, find_by when it might not
• Never call methods on find_by results without nil checking For more on Ruby & Rails Core, read ActiveRecord Ran 47 Identical Queries—Bullet Gem Found the Pattern.