La convención de la carpeta static

Your app needs CSS, JavaScript, and images. Flask gives them one default home: a folder named static next to your app. 📁

By convention, Flask serves anything inside the static folder automatically, so you never write a route to hand out a stylesheet yourself.

Place static right beside your app.py file. Flask finds it relative to your application package without any extra setup.

Files in that folder are reachable under the /static URL prefix. A file named style.css becomes available at /static/style.css in the browser.

You can nest folders inside static to stay tidy. The path on disk simply maps to the path in the URL, one to one.

So static/css/style.css is served at /static/css/style.css. The browser path mirrors your folder structure exactly. 🔗

The name static is a default, not a law. Flask uses it unless you tell it otherwise, which keeps every project predictable.

Pass static_folder when you create the app to point Flask at a differently named directory on disk.

You can also change the public prefix with static_url_path, so assets appear under /files instead of /static.

These files are static because Flask sends them as-is, with no Python running. That is exactly why serving them is so fast.

Do not put HTML you render into static. Dynamic pages belong in templates, while static holds only finished, ready-to-send assets.

You drop logo.png into the static folder. Where can the browser reach it?

You learned the static convention: drop assets in that folder and Flask serves them under /static, fast and free. Next, link them cleanly. ✨