The Flask Mega-Tutorial Part I: Hello, World!

Welcome! You are about to start on a journey to learn how to create web applications with Python and the Flask framework. The video above will give you an overview of the contents of this tutorial. In this first chapter, you are going to learn how to set up a Flask project. By the end of this chapter you are going to have a simple Flask web application running on your computer!

For your reference, below is a list of the articles in this series.

Note 1: If you are looking for the legacy version of this tutorial, it's here.

Note 2: If you would like to support my work on this blog, or just don't have patience to wait for weekly articles, I am offering the complete version of this tutorial packaged as an ebook or a set of videos. For more information, visit courses.miguelgrinberg.com.

All the code examples presented in this tutorial are hosted on a GitHub repository. Downloading the code from GitHub can save you a lot of typing, but I strongly recommend that you type the code yourself, at least for the first few chapters. Once you become more familiar with Flask and the example application you can access the code directly from GitHub if the typing becomes too tedious.

At the beginning of each chapter, I'm going to give you three GitHub links that can be useful while you work through the chapter. The Browse link will open the GitHub repository for Microblog at the place where the changes for the chapter you are reading were added, without including any changes introduced in future chapters. The Zip link is a download link for a zip file including the entire application up to and including the changes in the chapter. The Diff link will open a graphical view of all the changes that were made in the chapter you are about to read.

The GitHub links for this chapter are: Browse, Zip, Diff.

Installing Python

If you don't have Python installed on your computer, go ahead and install it now. If your operating system does not provide you with a Python package, you can download an installer from the Python official website. If you are using Microsoft Windows along with WSL or Cygwin, note that you will not be using the Windows native version of Python, but a Unix-friendly version that you need to obtain from Ubuntu (if you are using WSL) or from Cygwin.

To make sure your Python installation is functional, you can open a terminal window and type python3, or if that does not work, just python. Here is what you should expect to see:

$ python3
Python 3.5.2 (default, Nov 17 2016, 17:05:23)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> _

The Python interpreter is now waiting at an interactive prompt, where you can enter Python statements. In future chapters you will learn what kinds of things this interactive prompt is useful for. But for now, you have confirmed that Python is installed on your system. To exit the interactive prompt, you can type exit() and press Enter. On the Linux and Mac OS X versions of Python you can also exit the interpreter by pressing Ctrl-D. On Windows, the exit shortcut is Ctrl-Z followed by Enter.

Installing Flask

The next step is to install Flask, but before I go into that I want to tell you about the best practices associated with installing Python packages.

In Python, packages such as Flask are available in a public repository, from where anybody can download them and install them. The official Python package repository is called PyPI, which stands for Python Package Index (some people also refer to this repository as the "cheese shop"). Installing a package from PyPI is very simple, because Python comes with a tool called pip that does this work (in Python 2.7 pip does not come bundled with Python and needs to be installed separately).

To install a package on your machine, you use pip as follows:

$ pip install <package-name>

Interestingly, this method of installing packages will not work in most cases. If your Python interpreter was installed globally for all the users of your computer, chances are your regular user account is not going to have permission to make modifications to it, so the only way to make the command above work is to run it from an administrator account. But even without that complication, consider what happens when you install a package as above. The pip tool is going to download the package from PyPI, and then add it to your Python installation. From that point on, every Python script that you have on your system will have access to this package. Imagine a situation where you have completed a web application using version 0.11 of Flask, which was the most current version of Flask when you started, but now has been superseeded by version 0.12. You now want to start a second application, for which you'd like to use the 0.12 version, but if you replace the 0.11 version that you have installed you risk breaking your older application. Do you see the problem? It would be ideal if it was possible to install Flask 0.11 to be used by your old application, and also install Flask 0.12 for your new one.

To address the issue of maintaining different versions of packages for different applications, Python uses the concept of virtual environments. A virtual environment is a complete copy of the Python interpreter. When you install packages in a virtual environment, the system-wide Python interpreter is not affected, only the copy is. So the solution to have complete freedom to install any versions of your packages for each application is to use a different virtual environment for each application. Virtual environments have the added benefit that they are owned by the user who creates them, so they do not require an administrator account.

Let's start by creating a directory where the project will live. I'm going to call this directory microblog, since that is the name of the application:

$ mkdir microblog
$ cd microblog

If you are using a Python 3 version, virtual environment support is included in it, so all you need to do to create one is this:

$ python3 -m venv venv

With this command, I'm asking Python to run the venv package, which creates a virtual environment named venv. The first venv in the command is the name of the Python virtual environment package, and the second is the virtual environment name that I'm going to use for this particular environment. If you find this confusing, you can replace the second venv with a different name that you want to assign to your virtual environment. In general I create my virtual environments with the name venv in the project directory, so whenever I cd into a project I find its corresponding virtual environment.

Note that in some operating systems you may need to use python instead of python3 in the command above. Some installations use python for Python 2.x releases and python3 for the 3.x releases, while others map python to the 3.x releases.

After the command completes, you are going to have a directory named venv where the virtual environment files are stored.

If you are using any version of Python older than 3.4 (and that includes the 2.7 release), virtual environments are not supported natively. For those versions of Python, you need to download and install a third-party tool called virtualenv before you can create virtual environments. Once virtualenv is installed, you can create a virtual environment with the following command:

$ virtualenv venv

Regardless of the method you used to create it, you should have your virtual environment created. Now you have to tell the system that you want to use it, and you do that by activating it. To activate your brand new virtual environment you use the following command:

$ source venv/bin/activate
(venv) $ _

If you are using a Microsoft Windows command prompt window, the activation command is slightly different:

$ venv\Scripts\activate
(venv) $ _

When you activate a virtual environment, the configuration of your terminal session is modified so that the Python interpreter stored inside it is the one that is invoked when you type python. Also, the terminal prompt is modified to include the name of the activated virtual environment. The changes made to your terminal session are all temporary and private to that session, so they will not persist when you close the terminal window. If you work with multiple terminal windows open at the same time, it is perfectly fine to have different virtual environments activated on each one.

Now that you have a virtual environment created and activated, you can finally install Flask in it:

(venv) $ pip install flask

If you want to confirm that your virtual environment now has Flask installed, you can start the Python interpreter and import Flask into it:

>>> import flask
>>> _

If this statement does not give you any errors you can congratulate yourself, as Flask is installed and ready to be used.

A "Hello, World" Flask Application

If you go to the Flask website, you are welcomed with a very simple example application that has just five lines of code. Instead of repeating that trivial example, I'm going to show you a slightly more elaborate one that will give you a good base structure for writing larger applications.

The application will exist in a package. In Python, a sub-directory that includes a __init__.py file is considered a package, and can be imported. When you import a package, the __init__.py executes and defines what symbols the package exposes to the outside world.

Let's create a package called app, that will host the application. Make sure you are in the microblog directory and then run the following command:

(venv) $ mkdir app

The __init__.py for the app package is going to contain the following code:

app/__init__.py: Flask application instance

from flask import Flask

app = Flask(__name__)

from app import routes

The script above simply creates the application object as an instance of class Flask imported from the flask package. The __name__ variable passed to the Flask class is a Python predefined variable, which is set to the name of the module in which it is used. Flask uses the location of the module passed here as a starting point when it needs to load associated resources such as template files, which I will cover in Chapter 2. For all practical purposes, passing __name__ is almost always going to configure Flask in the correct way. The application then imports the routes module, which doesn't exist yet.

One aspect that may seem confusing at first is that there are two entities named app. The app package is defined by the app directory and the __init__.py script, and is referenced in the from app import routes statement. The app variable is defined as an instance of class Flask in the __init__.py script, which makes it a member of the app package.

Another peculiarity is that the routes module is imported at the bottom and not at the top of the script as it is always done. The bottom import is a workaround to circular imports, a common problem with Flask applications. You are going to see that the routes module needs to import the app variable defined in this script, so putting one of the reciprocal imports at the bottom avoids the error that results from the mutual references between these two files.

So what goes in the routes module? The routes are the different URLs that the application implements. In Flask, handlers for the application routes are written as Python functions, called view functions. View functions are mapped to one or more route URLs so that Flask knows what logic to execute when a client requests a given URL.

Here is your first view function, which you need to write in the new module named app/routes.py:

app/routes.py: Home page route

from app import app

def index():
    return "Hello, World!"

This view function is actually pretty simple, it just returns a greeting as a string. The two strange @app.route lines above the function are decorators, a unique feature of the Python language. A decorator modifies the function that follows it. A common pattern with decorators is to use them to register functions as callbacks for certain events. In this case, the @app.route decorator creates an association between the URL given as an argument and the function. In this example there are two decorators, which associate the URLs / and /index to this function. This means that when a web browser requests either of these two URLs, Flask is going to invoke this function and pass the return value of it back to the browser as a response. If this does not make complete sense yet, it will in a little bit when you run this application.

To complete the application, you need to have a Python script at the top-level that defines the Flask application instance. Let's call this script microblog.py, and define it as a single line that imports the application instance:

microblog.py: Main application module

from app import app

Remember the two app entities? Here you can see both together in the same sentence. The Flask application instance is called app and is a member of the app package. The from app import app statement imports the app variable that is a member of the app package. If you find this confusing, you can rename either the package or the variable to something else.

Just to make sure that you are doing everything correctly, below you can see a diagram of the project structure so far:


Believe it or not, this first version of the application is now complete! Before running it, though, Flask needs to be told how to import it, by setting the FLASK_APP environment variable:

(venv) $ export FLASK_APP=microblog.py

If you are using Microsoft Windows, use set instead of export in the command above.

Are you ready to be blown away? You can run your first web application, with the following command:

(venv) $ flask run
 * Serving Flask app "microblog"
 * Running on (Press CTRL+C to quit)

After the server initializes it will wait for client connections. The output from flask run indicates that the server is running on IP address, which is always the address of your own computer. This address is so common that is also has a simpler name that you may have seen before: localhost. Network servers listen for connections on a specific port number. Applications deployed on production web servers typically listen on port 443, or sometimes 80 if they do not implement encryption, but access to these ports require administration rights. Since this application is running in a development environment, Flask uses the freely available port 5000. Now open up your web browser and enter the following URL in the address field:


Alternatively you can use this other URL:


Do you see the application route mappings in action? The first URL maps to /, while the second maps to /index. Both routes are associated with the only view function in the application, so they produce the same output, which is the string that the function returns. If you enter any other URL you will get an error, since only these two URLs are recognized by the application.

Hello, World!

When you are done playing with the server you can just press Ctrl-C to stop it.

Congratulations, you have completed the first big step to become a web developer!

Before I end this chapter, I want to mention one more thing. Since environment variables aren't remembered across terminal sessions, you may find tedious to always have to set the FLASK_APP environment variable when you open a new terminal window. Starting with version 1.0, Flask allows you to register environment variables that you want to be automatically imported when you run the flask command. To use this option you have to install the python-dotenv package:

(venv) $ pip install python-dotenv

Then you can just write the environment variable name and value in a .flaskenv file in the top-level directory of the project:

.flaskenv: Environment variables for flask command


Doing this is optional. If you prefer to set the environment variable manually, that is perfectly fine, as long as you always remember to do it.


  • #451 Rouizi said 2020-08-24T07:31:41Z

    The best tutorial about programming on the internet, amazing Thank you so much

  • #452 Josh Puleo said 2020-09-08T20:34:17Z

    I am unable to create a virtual environment. I am on the newest version of python and when I try to create a virtual environment, nothing happens. So when I go to activate it, it says "The system cannot find the path specified."

    Do you know what I could do to fix that issue?

  • #453 Miguel Grinberg said 2020-09-08T21:51:10Z

    @Josh: Nothing happens? That's really unlikely. Do you get the virtual environment directory created? Does the command print anything to your screen?

  • #454 Nomk said 2020-09-15T03:26:56Z

    Awesome! Thank you

  • #455 latin bishop said 2020-10-23T23:05:25Z

    Having problems on chromebook connecting from different divce after doing port forwarding .

  • #456 Miguel Grinberg said 2020-10-23T23:16:35Z

    @latin: At this stage in the tutorial access from other devices is not enabled, so what you are seeing is normal.

  • #457 Anozie Joseph Kelechi said 2020-10-26T13:57:12Z

    I have an issue with pipenv shell,my project directory is set at:user/my name/Desktop/myappname but if I run pipenv shell instead of it to activate my current working directory which is:user/myname/Desktop/myappname it will activate:user/myname bash3.2$ any way to solve this issue I be greatfull Am using MacBook air

  • #458 Miguel Grinberg said 2020-10-26T15:43:35Z

    @Anozie: I do not use pipenv myself. Have you considered following the instructions provided in this article instead of using pipenv if that does not work for you?

  • #459 Rubzzz06 said 2020-10-26T23:12:42Z

    Hi Miguel, thanks for this tuto. I have been following step by step your code, but when I run flask I get the following error message any idea what shall I do; (VirtEnv) $ flask run * Serving Flask app "testapp.py" * Environment: production WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead. * Debug mode: off Usage: flask run [OPTIONS]

    Error: Could not import "testapp".

  • #460 Miguel Grinberg said 2020-10-26T23:20:01Z

    @Rubzzz06: you don't seem to be following it accurately, there is no testapp.py in this tutorial. What is testapp.py?

  • #461 Rubzzz06 said 2020-10-27T23:58:57Z

    @MiguelGrinberg: you are right I was not saving files (testapp.py = microblog.py) in the right directory. But I found the issue and now it's solved. Thanks Miguel. Going through the rest of the tuto - very exciting, I wonder if you have more guide through tutos like this one with different projects. I really enjoy the way it is instructed.


  • #462 Bilal Junaidy said 2020-10-29T12:30:14Z

    Hi Miguel, Thank you very much for creating this Flask by example series. Really appreciate the time and effort you have put into this. I am a little confused about the structure you have used to create this application. Previously whenever I would create a flask application, I simply create a python file (so lets say blog.py), and then in the command line, I simply use the "set FLASK_APP=blog.py", and then follow that with the "flask run" command to run the application. In the blog.py file, I import Flask from flask, as well as create the instance of the flask application by using "app = Flask(name)".

    However, in your tutorial above, you have used a different approach, and I can not seem to follow how the "flask run" command interprets the various python files you have created. For example, what is the purpose of creating the microblog.py file and adding "from app import app" in this file. Another example was why there was a need to create a "init.py" file and then a "route.py" file. Would it not have been better had we included everything in the same python file?

    Looking forward to hearing from you. Again, thank you very much for creating this flask by example series. I really appreciate it. Bilal

  • #463 Miguel Grinberg said 2020-10-29T14:02:41Z

    @Bilal: Flask does not care about how you structure your application. A single file app is fine for small projects, but this tutorial grows to be fairly large, so I'm using a better structure that can scale. The microblog.py file is your app entry point, this is why FLASK_APP is set to this file.

  • #464 Henry Wu Hu said 2020-11-01T23:48:43Z

    Hi. Miguel, Pleased to meet you. I am enrolled in your flask course Currenlty I am replicating the db creation procedure in models.py. When I try to run the code using the terminal window

    from app.models import User u = User(something....) I get the following error

    ' No module name 'app'

    Attached is a portion of my init.py file

    from flask import Flask from app.config import Config from flask_sqlalchemy import SQLAlchemy from flask_migrate import Migrate

    app = Flask(name) app.config.from_object(Config) db = SQLAlchemy(app) migrate = Migrate (app,db)

    from app import routes, models

    Best Regards

  • #465 Miguel Grinberg said 2020-11-02T20:00:11Z

    @Henry: the error is telling you that an "app" package does not exist in your project? Did you name your application package differently? You have to use the name of your package when you say from [package].models import User.

  • #466 Ian Elliot Goodman said 2020-11-05T04:06:10Z


    I've followed chapter 1 of your tutorial very closely multiple times today and have tried troubleshooting on google but haven't figured out how to avoid an error when initiating "flask run." I keep receiving the message, "Error: Failed to find Flask application or factory in module "microblog". Use "FLASK_APP=microblog:name to specify one." If you have any suggestions to fix this issue I would be so grateful!

  • #467 Miguel Grinberg said 2020-11-05T09:45:24Z

    @Ian: I don't have any suggestions, but I do have two questions for you.

    What value did you set in your FLASK_APP variable? What code do you have in the file microblog.py?
  • #468 Mohammed Shinoy said 2020-11-10T12:23:47Z

    Is there a difference between this blog based course and the course on the https://courses.miguelgrinberg.com/p/flask-mega-tutorial

  • #469 Miguel Grinberg said 2020-11-10T23:36:18Z

    @Mohammed: Yes, the blog version is text only, while the version in my courses site has about 11 hours of video in addition to the written material.

  • #470 Ian Goodman said 2020-11-11T17:48:47Z

    Hey Miguel,

    Thanks for your help, im excited to make progress in the tutorial. It appears I have gotten flask run to work, but receive a 404 error when I past in the url's for "localhost:5000" and "/index", I have double checked my code that routes was init.py and routes.py are set properly. but I keep getting a message that url is not found on the server. Please let me know if you're familiar with this issue! Thank you for all your help!

  • #471 Miguel Grinberg said 2020-11-11T19:10:56Z

    @Ian: are you sure you are typing the URL correctly? What you need to type is http://localhost:5000 or http://localhost:5000/index. Note that there is a single colon between localhost and 5000, not two.

  • #472 Ray Ng said 2020-11-15T14:27:31Z

    I too experienced this microBlog not found error.


    For me, the issue was resolved by cd-ing into the directory that contained microBlog.py and then running flask run in the terminal.

  • #473 Agustin said 2020-12-22T14:00:13Z

    This mega tutorial is awesome, really helpfull!

    thank you so much!

  • #474 steve hepple said 2021-01-01T14:37:54Z

    Then you can just write the environment variable name and value in a .flaskenv file in the top-level directory of the project:

    .flaskenv: Environment variables for flask command

    FLASK_APP=microblog.py Sorry...but what is a .flaskenv file and how should work it into the tutorial....Many thanks.

  • #475 Miguel Grinberg said 2021-01-01T18:07:58Z

    @steve: I don't understand the question. The .flaskenv file is just a file, where you write the contents indicated in the tutorial. If you want to learn more about how .flaskenv files work with Flask, see the Flask documentation: https://flask.palletsprojects.com/en/1.1.x/cli/#environment-variables-from-dotenv.

Leave a Comment