---
title: "Jak zarządzać plikami statycznymi (np. obrazy, JavaScript, CSS)"
version: 5.1
locale: pl
source: https://docs.djangoproject.com/pl/5.1/howto/static-files/
canonical: https://djangodocs.dev/pl/5.1/howto/static-files/
---
# Jak zarządzać plikami statycznymi (np. obrazy, JavaScript, CSS)

Strony internetowe na ogół wymagają serwowania dodatkowych plików takich jak zdjęcia, skrypty JavaScript lub style CSS. W Django nazywamy te pliki „plikami statycznymi”. \_Django zapewnia [`django.contrib.staticfiles`](/pl/5.1/ref/contrib/staticfiles/#module-django.contrib.staticfiles), aby ułatwić zarządzanie nimi.

Ta strona opisuje jak możesz serwować te pliki statyczne.

## Konfigurowanie plików statycznych

1. Make sure that `django.contrib.staticfiles` is included in your
   [`INSTALLED_APPS`](/pl/5.1/ref/settings/#std-setting-INSTALLED_APPS).
2. In your settings file, define [`STATIC_URL`](/pl/5.1/ref/settings/#std-setting-STATIC_URL), for example:

   ```
   STATIC_URL = "static/"
   ```
3. In your templates, use the [`static`](/pl/5.1/ref/templates/builtins/#std-templatetag-static) template tag to build the URL for
   the given relative path using the configured `staticfiles`
   [`STORAGES`](/pl/5.1/ref/settings/#std-setting-STORAGES) alias.

   ```html+django
   {% load static %}
   <img src="{% static 'my_app/example.jpg' %}" alt="My image">
   ```
4. Store your static files in a folder called `static` in your app. For
   example `my_app/static/my_app/example.jpg`.

> **Serwowanie plików**
>
> In addition to these configuration steps, you’ll also need to actually
> serve the static files.
>
> During development, if you use [`django.contrib.staticfiles`](/pl/5.1/ref/contrib/staticfiles/#module-django.contrib.staticfiles), this will
> be done automatically by [`runserver`](/pl/5.1/ref/django-admin/#django-admin-runserver) when [`DEBUG`](/pl/5.1/ref/settings/#std-setting-DEBUG) is set
> to `True` (see [`django.contrib.staticfiles.views.serve()`](/pl/5.1/ref/contrib/staticfiles/#django.contrib.staticfiles.views.serve)).
>
> Ta metoda jest **skrajnie nieefektywna** i prawdopodobnie **niebezpieczna**, więc jest **nieodpowiednia** do celów produkcyjnych,
>
> Zobacz [How to deploy static files](/pl/5.1/howto/static-files/deployment/), aby wybrać odpowiednią strategię serwowania plików statycznych w środowisku produkcyjnym.

Your project will probably also have static assets that aren’t tied to a
particular app. In addition to using a `static/` directory inside your apps,
you can define a list of directories ([`STATICFILES_DIRS`](/pl/5.1/ref/settings/#std-setting-STATICFILES_DIRS)) in your
settings file where Django will also look for static files. For example:

```
STATICFILES_DIRS = [
    BASE_DIR / "static",
    "/var/www/static/",
]
```

See the documentation for the [`STATICFILES_FINDERS`](/pl/5.1/ref/settings/#std-setting-STATICFILES_FINDERS) setting for
details on how `staticfiles` finds your files.

> **Przestrzeń nazw plików statycznych**
>
> Now we *might* be able to get away with putting our static files directly
> in `my_app/static/` (rather than creating another `my_app`
> subdirectory), but it would actually be a bad idea. Django will use the
> first static file it finds whose name matches, and if you had a static file
> with the same name in a *different* application, Django would be unable to
> distinguish between them. We need to be able to point Django at the right
> one, and the best way to ensure this is by *namespacing* them. That is,
> by putting those static files inside *another* directory named for the
> application itself.
>
> You can namespace static assets in [`STATICFILES_DIRS`](/pl/5.1/ref/settings/#std-setting-STATICFILES_DIRS) by
> specifying [prefixes](/pl/5.1/ref/settings/#staticfiles-dirs-prefixes).

## Serwowanie plików statycznych podczas rozwoju projektu

If you use [`django.contrib.staticfiles`](/pl/5.1/ref/contrib/staticfiles/#module-django.contrib.staticfiles) as explained above,
[`runserver`](/pl/5.1/ref/django-admin/#django-admin-runserver) will do this automatically when [`DEBUG`](/pl/5.1/ref/settings/#std-setting-DEBUG) is set
to `True`. If you don’t have `django.contrib.staticfiles` in
[`INSTALLED_APPS`](/pl/5.1/ref/settings/#std-setting-INSTALLED_APPS), you can still manually serve static files using the
[`django.views.static.serve()`](/pl/5.1/ref/views/#django.views.static.serve) view.

To nie jest odpowiednie do zastosowań produkcyjnych! Aby poznać popularne strategie wdrożeniowe, zobacz [How to deploy static files](/pl/5.1/howto/static-files/deployment/).

For example, if your [`STATIC_URL`](/pl/5.1/ref/settings/#std-setting-STATIC_URL) is defined as `static/`, you can
do this by adding the following snippet to your `urls.py`:

```
from django.conf import settings
from django.conf.urls.static import static

urlpatterns = [
    # ... the rest of your URLconf goes here ...
] + static(settings.STATIC_URL, document_root=settings.STATIC_ROOT)
```

> **Note**
>
> This helper function works only in debug mode and only if
> the given prefix is local (e.g. `static/`) and not a URL (e.g.
> `http://static.example.com/`).
>
> Also this helper function only serves the actual [`STATIC_ROOT`](/pl/5.1/ref/settings/#std-setting-STATIC_ROOT)
> folder; it doesn’t perform static files discovery like
> [`django.contrib.staticfiles`](/pl/5.1/ref/contrib/staticfiles/#module-django.contrib.staticfiles).
>
> Finally, static files are served via a wrapper at the WSGI application
> layer. As a consequence, static files requests do not pass through the
> normal [middleware chain](/pl/5.1/topics/http/middleware/).

## Serwowanie plików przesłanych przez użytkownika w trakcie rozwoju projektu

During development, you can serve user-uploaded media files from
[`MEDIA_ROOT`](/pl/5.1/ref/settings/#std-setting-MEDIA_ROOT) using the [`django.views.static.serve()`](/pl/5.1/ref/views/#django.views.static.serve) view.

To nie jest odpowiednie do zastosowań produkcyjnych! Aby poznać popularne strategie wdrożeniowe, zobacz [How to deploy static files](/pl/5.1/howto/static-files/deployment/).

For example, if your [`MEDIA_URL`](/pl/5.1/ref/settings/#std-setting-MEDIA_URL) is defined as `media/`, you can do
this by adding the following snippet to your [`ROOT_URLCONF`](/pl/5.1/ref/settings/#std-setting-ROOT_URLCONF):

```
from django.conf import settings
from django.conf.urls.static import static

urlpatterns = [
    # ... the rest of your URLconf goes here ...
] + static(settings.MEDIA_URL, document_root=settings.MEDIA_ROOT)
```

> **Note**
>
> This helper function works only in debug mode and only if
> the given prefix is local (e.g. `media/`) and not a URL (e.g.
> `http://media.example.com/`).

## Testowanie

When running tests that use actual HTTP requests instead of the built-in
testing client (i.e. when using the built-in [`LiveServerTestCase`](/pl/5.1/topics/testing/tools/#django.test.LiveServerTestCase)) the static assets need to be served along
the rest of the content so the test environment reproduces the real one as
faithfully as possible, but `LiveServerTestCase` has only very basic static
file-serving functionality: It doesn’t know about the finders feature of the
`staticfiles` application and assumes the static content has already been
collected under [`STATIC_ROOT`](/pl/5.1/ref/settings/#std-setting-STATIC_ROOT).

Because of this, `staticfiles` ships its own
[`django.contrib.staticfiles.testing.StaticLiveServerTestCase`](/pl/5.1/ref/contrib/staticfiles/#django.contrib.staticfiles.testing.StaticLiveServerTestCase), a subclass
of the built-in one that has the ability to transparently serve all the assets
during execution of these tests in a way very similar to what we get at
development time with `DEBUG = True`, i.e. without having to collect them
using [`collectstatic`](/pl/5.1/ref/contrib/staticfiles/#django-admin-collectstatic) first.

## Wdrażanie

[`django.contrib.staticfiles`](/pl/5.1/ref/contrib/staticfiles/#module-django.contrib.staticfiles) provides a convenience management command
for gathering static files in a single directory so you can serve them easily.

1. Set the [`STATIC_ROOT`](/pl/5.1/ref/settings/#std-setting-STATIC_ROOT) setting to the directory from which you’d
   like to serve these files, for example:

   ```
   STATIC_ROOT = "/var/www/example.com/static/"
   ```
2. Run the [`collectstatic`](/pl/5.1/ref/contrib/staticfiles/#django-admin-collectstatic) management command:

   ```shell
   $ python manage.py collectstatic
   ```

   This will copy all files from your static folders into the
   [`STATIC_ROOT`](/pl/5.1/ref/settings/#std-setting-STATIC_ROOT) directory.
3. Use a web server of your choice to serve the
   files. [How to deploy static files](/pl/5.1/howto/static-files/deployment/) covers some common deployment
   strategies for static files.

## Czytaj więcej

This document has covered the basics and some common usage patterns. For
complete details on all the settings, commands, template tags, and other pieces
included in [`django.contrib.staticfiles`](/pl/5.1/ref/contrib/staticfiles/#module-django.contrib.staticfiles), see [the staticfiles
reference](/pl/5.1/ref/contrib/staticfiles/).