Difference Between null=True and blank=True in Django Models

Django, a popular Python web framework, offers powerful tools for building robust and flexible database-backed web applications. When defining models in Django, developers often encounter two common field options: null=True and blank=True. These options seem similar at first glance but serve different purposes. In this blog, we’ll learn difference between null=True and blank=True in Django models, using practical examples to illustrate their usage

null=True in Django Model

The null option in Django models is primarily related to database storage. When you set null=True on a field, it means that the corresponding database column can store NULL values. In other words, if a record does not have value for this field, it will be stored as NULL in the database.

Let’s consider an example to illustrate the use of null=True:

from django.db import models

class UserProfile(models.Model):
    username = models.CharField(max_length=50)
    bio = models.TextField(null=True)

In this example, the bio field allows NULL values in the database,. This means that some UserProfile records can have no bio information, and the bio column in the database will store NULL for those records.

blank=True in Django Model

On the other hand, the blank option in Django models is related to form validation. When you set blank=True on field, it indicates that the field can be left blank in a form. This is relevant for Django’s form validation, not just database storage.

Here’s an example:

from django.db import models

class Article(models.Model):
    title = models.CharField(max_length=100)
    content = models.TextField(blank=True)

In this case, the content field can be left empty when creating an Article instance using a form. It won’t trigger a validation error if the user submits the form without providing content for the article.

When to Use null=True vs. blank=True

  1. null=True:
  • Use null=True when you want to allow the database to store NULL values for a field.
  • It’s suitable for fields that represent database-level constraints, such as optional foreign keys or numeric values.
  • Use cases may include situations where you want to distinguish between an empty value and a NULL value in the database.
  1. blank=True:
  • Use blank=True when you want to permit form submissions with empty values for a field.
  • It’s typically used for fields that are optional from a user’s perspective.
  • Common use cases include text fields like descriptions, comments, or optional details in a form.

Combining null=True and blank=True

You can use both null=True and blank=True together for a field if you want to allow NULL values in the database and also permit empty form submissions. This combination offers maximum flexibility.

from django.db import models

class Book(models.Model):
    title = models.CharField(max_length=100)
    author = models.CharField(max_length=50, null=True, blank=True)

In this example, the author field can be left empty in forms, and it can also have NULL values in the database.


Understanding the distinctions between null=True and blank=True is essential for designing Django models effectively. These options provide control over database storage and form validation, respectively. By using them appropriately, you can build Django applications that are both user-friendly and efficient in handling data. Whether you need optional fields, nullable database columns, or combination of both, Django’s null and blank options offer the flexibility to meet your requirements.