The Messages Framework

Django's messages framework is a built-in system for showing one-time "flash" notifications — short status messages like "Profile saved!" or "Login failed" that appear once after an action and then disappear, surviving the redirect that usually follows a form submission.

Learn The Messages Framework in our free Django course — a beginner-friendly interactive lesson with worked examples, a practice exercise and a quick reference.

Part of the free Django course at LearnCodingFast — hands-on lessons with examples you run in your browser, plus practice exercises and a quick quiz.

In this lesson you'll learn how to add messages with messages.success() , messages.error() , messages.info() , and messages.warning() , how to display them in a template, and how message tags let you style each level differently.

The messages framework lets a view attach a short notification to the current request. You import django.contrib.messages as messages and call one of its level methods, passing the request and the text to show.

The most common pattern is "do something, add a message, then redirect." Because the message is stored between the redirect and the next page, the user reliably sees it even though they land on a brand-new request.

Once a view has added messages, your template displays them by looping over the messages variable that Django's context processor makes available. Each message has a tags attribute (like success or error ) you can drop straight into a CSS class.

Here alert-{'{ message.tags }'} renders to something like alert-success or alert-error , letting you give each severity its own colour. Messages are consumed once read, so they appear exactly once and then vanish.

Django provides five severity levels, each with its own convenience method and default tag. Choosing the right one tells the user how important a notification is and lets your CSS colour it appropriately.

If your CSS framework expects different class names (for example Bootstrap uses danger instead of error ), you can remap the tags in settings.py with MESSAGE_TAGS .

Fill in the blank with the correct messages method so a successful save shows a green success notification.

❌ Messages added but nothing shows on the page

Your template never loops over the messages variable.

✅ Fix: add a {' '} loop to your base template.

❌ MessageFailure: You cannot add messages without...

The message middleware or context processor is missing.

✅ Fix: ensure django.contrib.messages is in INSTALLED_APPS and its middleware is enabled.

You rendered the messages list more than once on the page.

✅ Fix: loop over messages in exactly one place, usually the base template.

Write a function that adds the right message for each checkout outcome: success when paid, warning when low stock, and error when the card is declined.

Lesson complete — you can flash messages to your users!

You now know how to add messages with the level methods, display them in a template by looping over messages , and style each level using its tag or a custom MESSAGE_TAGS mapping.

🚀 Up next: User Authentication — log users in and out, and protect views with login_required.

Practice quiz

• Browse all free courses
• Cheat sheets & quizzes
• Coding dictionary