URL_for with static files in Flask - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of url_for('static', filename='...') in Flask?

It generates the correct URL to access static files like CSS, JavaScript, or images stored in the static folder of a Flask app.

beginner

Where should static files be placed in a Flask project to be served correctly?

Static files should be placed inside the static folder at the root of the Flask project.

beginner

How do you use url_for to link a CSS file named style.css located in the static folder?

Use url_for('static', filename='style.css') inside your HTML template to get the URL for style.css.

intermediate

Why is it better to use url_for('static', filename='...') instead of hardcoding static file paths?

Because url_for automatically handles URL building, including any changes in app structure or deployment settings, making your links reliable and portable.

intermediate

What happens if you try to access a static file that does not exist using url_for('static', filename='missing.png')?

The URL will still be generated, but when accessed in the browser, it will return a 404 error because the file is missing.

What argument do you pass to url_for to get a static file URL?

A 'route'

B 'static'

C 'template'

D 'file'

You use url_for('static', filename='...') to get URLs for static files.

Where should you place your CSS and image files in a Flask project?

A Inside the <code>static</code> folder

B Inside the <code>templates</code> folder

C In the root project folder

D Inside the <code>views</code> folder

Static files belong in the static folder so Flask can serve them properly.

What does url_for('static', filename='js/app.js') return?

A An error because of the slash in filename

B The content of the <code>app.js</code> file

C The URL path to the <code>app.js</code> file inside the <code>static/js</code> folder

D The URL to a Flask route named 'js/app.js'

It returns the URL to the static file app.js inside the js folder.

Why should you avoid hardcoding static file URLs in Flask templates?

A Because static files cannot be accessed without <code>url_for</code>

B Because hardcoded URLs are slower to load

C Because Flask does not allow hardcoded URLs

D Because <code>url_for</code> handles URL changes and deployment differences automatically

url_for makes your app flexible by adapting URLs if the app structure or deployment changes.

What HTTP status code will you get if a static file URL generated by url_for points to a missing file?

A 404 Not Found

B 301 Moved Permanently

C 200 OK

D 500 Internal Server Error

If the file is missing, the server returns a 404 Not Found error when the URL is accessed.

Explain how to use url_for to link a static image in a Flask template.

Think about how Flask knows where static files live and how to build their URLs.

Why is using url_for('static', filename='...') considered a best practice over hardcoding static file paths?

Consider what happens if you move your app or change folder names.