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.


  • #326 Miguel Grinberg said 2019-08-23T15:00:27Z

    @not quite: there is currently one known problem. What does not work is running in debug mode on Windows. This is a bug in Werkzeug. Other problems I'm not aware of, my guess is that the problem is on your side, maybe missing or misconfigured FLASK_APP variable.

  • #327 aaron kigler said 2019-08-28T01:55:16Z

    i have been reading through your blog and i was curious if all of this information is up to date or should I use a newer tutorial? also thanks for ur work

  • #328 Miguel Grinberg said 2019-08-28T07:20:02Z

    @aaron: Yes, this tutorial is actively maintained and is up to date.

  • #329 Victor Inojosa said 2019-09-01T00:56:08Z

    Thanks Miguel! for this great tutorial. I know it's just the start, but I've learned much more about a few things like the environment variable setup and the package style from the very beginning. Thanks... Now I move forward to the next Chapter ;-)

  • #330 von Paulus said 2019-09-02T18:20:17Z

    Hi, I took your Flask tutorial from 2014 from a friend. And then I went to your site. Where should I continue after the first chapter, here on the website or in the book, maybe something will not be enough here.

    I look forward to hearing

  • #331 Miguel Grinberg said 2019-09-02T18:30:28Z

    @von Paulus: the Flask Web Development book is not the same as this tutorial, they are different. If you have the 2014 edition of the book it is not a bit outdated, there's been a new edition of the book that came out in 2018. This tutorial is also up to date with recent releases of Flask.

  • #332 akkhil said 2019-09-08T18:32:15Z

    excellent tutorial! very helpful.. but i get an error failed to find Flask application or factory in module "microblog". use FLASK_APP=microblog:name to specify one. please help me resolve this

  • #333 Miguel Grinberg said 2019-09-09T10:16:21Z

    @akkhil: you don't seem to have an app variable in microblog.py. Use the download link at the top of this article to get a working copy of the project to compare against if you need to find your mistake.

  • #334 João Matos said 2019-09-09T16:13:21Z

    Hello Miguel, is there a reason for you to associate both / and /index to the same view function?

  • #335 Miguel Grinberg said 2019-09-10T12:58:28Z

    @João: just to demonstrate that it can be done, no real reason.

  • #336 Steven said 2019-09-27T08:03:20Z

    Hello Miguel,

    Very nice tutorial!I want to know what version of flask you were used in this tutorial?

  • #337 Rob Pilcher said 2019-09-29T06:48:08Z

    hey man. Thanks so much for this. One problem - I keep getting an error message from my cmd window when trying to run flask by entering "flask run" saying:

    Serving Flask app "microblog.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 "microblog".

    Not sure what I'm doing but I've followed https://aryaboudaie.com/python/technical/educational/web/flask/2018/10/17/flask.html and managed to get the correct result from running the instruction from within Pycharm. Could it be a path issue?



  • #338 Miguel Grinberg said 2019-09-29T21:44:55Z

    @Steven: all recent versions of Flask are compatible with this tutorial, including the current 1.1.1.

  • #339 Miguel Grinberg said 2019-09-29T21:48:38Z

    @Rob: it could be that the top-level directory is not in your Python path, or else that you have placed microblog.py in the wrong location. It should be in the top-level directory.

  • #340 Alex said 2019-10-06T22:48:12Z

    To people getting "Could not import "microblog" or "failed to find Flask application or factory in module "microblog", see the official guide on how to structure your application as a module https://flask.palletsprojects.com/en/1.1.x/patterns/packages/

  • #341 Miguel Grinberg said 2019-10-07T22:00:37Z

    @Alex: that's a different approach than the one followed by this tutorial. Definitely good to know about it, but if you get the "could not import microblog" error it means that you have veered away from this tutorial in some way.

  • #342 Jay said 2019-10-09T23:10:00Z

    Can you give a little more details in to this?

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

    I used touch .flaskenv but the file format is not recognized. Do I need to insert it via the command line?

  • #343 Miguel Grinberg said 2019-10-10T09:54:15Z

    @Jay: you need to create a file calls .flaskenv with the text editor of your choice, and write the environment variable assignment as shown in the article above.

  • #344 Jeff said 2019-10-26T11:48:03Z

    Hi Miguel. In going through Chapter_1 everything worked and I got the 'Hello World' in the browser at the end. Great !! However, on closing out of the terminal and then going back in (to make sure it all still worked) - on entering '$ flask run' I get the Error: Could not import "microblog". I notice that in my microblog directory there were some pycache directories added after this first execution (not sure if that is relevant). If I delete all the files from the microblog directory and start from scratch, then it works again (and then not on second execution, i.e. this problem persists). So it seems that on execution there is some bug that occurs that prevents a second use. Any revelations here most welcome!! thanks - Jeff

  • #345 Jeff said 2019-10-26T12:15:57Z

    sorry about my last post: I wasn't in the microblog directory - simple solution for a simple mind

  • #346 min said 2019-10-26T12:53:05Z

    thank you very much for this great tutorials!

  • #347 Hassan said 2019-10-28T16:25:11Z

    Good tutorial but I feel like the writer has introduced unnecessary name collisions in the code which create confusion for the inexperienced.

  • #348 Miguel Grinberg said 2019-10-29T01:54:00Z

    @Hassan: Fair criticism. I have opted to explain these name collisions that are often seen in production code instead of avoid them.

  • #349 Mark Chassy said 2019-10-29T14:31:14Z


    I am working through this tutorial, and it is very clear except for the from app import app ;-) Where would I change the name of app to microblog ? Just so I can see the difference.

  • #350 Miguel Grinberg said 2019-10-30T12:05:59Z

    @Mark: the first "app" is the package. This is the app subdirectory. You can rename this subdirectory to "myapp" or whatever else you like, then use "from myapp import app".

Leave a Comment