Soft Delete vs Hard Delete — What's the Difference?

A hard delete permanently removes a row from the database; a soft delete instead marks a row as deleted (typically with a deleted_at timestamp or is_deleted...

Published October 6, 2026

A hard delete removes the row permanently; a soft delete marks it as deleted (a deleted_at timestamp) and hides it from normal queries so it can be restored or audited. Soft delete is safer, hard delete is simpler and required for privacy erasure.

The concept

Soft delete keeps history and makes undo trivial, but every query must filter out deleted rows and unique constraints get awkward.

Hard delete keeps tables small and meets legal erasure requests. Many systems soft delete first, then purge after a retention period.

What happens to the row

DELETE FROM users WHERE id = 7;
row gone forever
UPDATE users SET deleted_at = NOW() WHERE id = 7;
row stays, hidden, restorable

Practical examples

Laravel soft deletes

use Illuminate\Database\Eloquent\SoftDeletes;
class Post extends Model { use SoftDeletes; }
$post->delete();     // sets deleted_at
$post->restore();
$post->forceDelete();

Query only active rows

SELECT * FROM posts WHERE deleted_at IS NULL;

Purge old soft-deleted rows

DELETE FROM posts WHERE deleted_at < NOW() - INTERVAL 90 DAY;

Common mistakes

  • Forgetting the deleted_at filter in raw queries.
  • Unique indexes clashing with soft-deleted duplicates.
  • Keeping personal data forever when users ask to be erased.

Key takeaways

  • Soft = flag, hard = remove.
  • Soft delete needs query discipline.
  • Purge on a schedule.

FAQ

Which should I default to?

Soft delete for business data you may restore; hard delete for logs and personal data requests.

Does soft delete help audits?

Yes, but a dedicated audit log is more reliable.

More SQL articles