---
title: "Unggah Berkas"
version: 2.1
locale: id
source: https://docs.djangoproject.com/id/2.1/topics/http/file-uploads/
canonical: https://djangodocs.dev/id/2.1/topics/http/file-uploads/
---
# Unggah Berkas

When Django handles a file upload, the file data ends up placed in
[`request.FILES`](/id/2.1/ref/request-response/#django.http.HttpRequest.FILES) (for more on the
`request` object see the documentation for [request and response objects](/id/2.1/ref/request-response/)). This document explains how files are stored on disk
and in memory, and how to customize the default behavior.

> **Warning**
>
> There are security risks if you are accepting uploaded content from
> untrusted users! See the security guide's topic on
> [User-uploaded content](/id/2.1/topics/security/#user-uploaded-content-security) for mitigation details.

## Unggah berkas dasar

Consider a simple form containing a [`FileField`](/id/2.1/ref/forms/fields/#django.forms.FileField):

*forms.py*

```python
from django import forms

class UploadFileForm(forms.Form):
    title = forms.CharField(max_length=50)
    file = forms.FileField()
```

A view handling this form will receive the file data in
[`request.FILES`](/id/2.1/ref/request-response/#django.http.HttpRequest.FILES), which is a dictionary
containing a key for each [`FileField`](/id/2.1/ref/forms/fields/#django.forms.FileField) (or
[`ImageField`](/id/2.1/ref/forms/fields/#django.forms.ImageField), or other [`FileField`](/id/2.1/ref/forms/fields/#django.forms.FileField)
subclass) in the form. So the data from the above form would
be accessible as `request.FILES['file']`.

Note that [`request.FILES`](/id/2.1/ref/request-response/#django.http.HttpRequest.FILES) will only
contain data if the request method was `POST` and the `<form>` that posted
the request has the attribute `enctype="multipart/form-data"`. Otherwise,
`request.FILES` will be empty.

Most of the time, you'll simply pass the file data from `request` into the
form as described in [Mengikat berkas terunggah ke formulir](/id/2.1/ref/forms/api/#binding-uploaded-files). This would look
something like:

*views.py*

```python
from django.http import HttpResponseRedirect
from django.shortcuts import render
from .forms import UploadFileForm

# Imaginary function to handle an uploaded file.
from somewhere import handle_uploaded_file

def upload_file(request):
    if request.method == 'POST':
        form = UploadFileForm(request.POST, request.FILES)
        if form.is_valid():
            handle_uploaded_file(request.FILES['file'])
            return HttpResponseRedirect('/success/url/')
    else:
        form = UploadFileForm()
    return render(request, 'upload.html', {'form': form})
```

Notice that we have to pass [`request.FILES`](/id/2.1/ref/request-response/#django.http.HttpRequest.FILES)
into the form's constructor; this is how file data gets bound into a form.

Ini adalah cara umum anda mungkin menangani sebuah berkas terunggah:

```
def handle_uploaded_file(f):
    with open('some/file/name.txt', 'wb+') as destination:
        for chunk in f.chunks():
            destination.write(chunk)
```

Looping over `UploadedFile.chunks()` instead of using `read()` ensures that
large files don't overwhelm your system's memory.

There are a few other methods and attributes available on `UploadedFile`
objects; see [`UploadedFile`](/id/2.1/ref/files/uploads/#django.core.files.uploadedfile.UploadedFile) for a complete reference.

### Penanganan berkas terunggah dengan model

Jika anda sedang menyimpan sebuah berkas pada [`Model`](/id/2.1/ref/models/instances/#django.db.models.Model) dengan [`FileField`](/id/2.1/ref/models/fields/#django.db.models.FileField), menggunakan [`ModelForm`](/id/2.1/topics/forms/modelforms/#django.forms.ModelForm) memuat pengolahan ini lebih mudah. byek berkas akan disimpan ke tempat ditentukan oleh argumen [`upload_to`](/id/2.1/ref/models/fields/#django.db.models.FileField.upload_to) dari [`FileField`](/id/2.1/ref/models/fields/#django.db.models.FileField)  sesuai ketika memanggil `form.save()`:

```
from django.http import HttpResponseRedirect
from django.shortcuts import render
from .forms import ModelFormWithFileField

def upload_file(request):
    if request.method == 'POST':
        form = ModelFormWithFileField(request.POST, request.FILES)
        if form.is_valid():
            # file is saved
            form.save()
            return HttpResponseRedirect('/success/url/')
    else:
        form = ModelFormWithFileField()
    return render(request, 'upload.html', {'form': form})
```

If you are constructing an object manually, you can simply assign the file
object from [`request.FILES`](/id/2.1/ref/request-response/#django.http.HttpRequest.FILES) to the file
field in the model:

```
from django.http import HttpResponseRedirect
from django.shortcuts import render
from .forms import UploadFileForm
from .models import ModelWithFileField

def upload_file(request):
    if request.method == 'POST':
        form = UploadFileForm(request.POST, request.FILES)
        if form.is_valid():
            instance = ModelWithFileField(file_field=request.FILES['file'])
            instance.save()
            return HttpResponseRedirect('/success/url/')
    else:
        form = UploadFileForm()
    return render(request, 'upload.html', {'form': form})
```

### Uploading multiple files

If you want to upload multiple files using one form field, set the `multiple`
HTML attribute of field's widget:

*forms.py*

```python
from django import forms

class FileFieldForm(forms.Form):
    file_field = forms.FileField(widget=forms.ClearableFileInput(attrs={'multiple': True}))
```

Then override the `post` method of your
[`FormView`](/id/2.1/ref/class-based-views/generic-editing/#django.views.generic.edit.FormView) subclass to handle multiple file
uploads:

*views.py*

```python
from django.views.generic.edit import FormView
from .forms import FileFieldForm

class FileFieldView(FormView):
    form_class = FileFieldForm
    template_name = 'upload.html'  # Replace with your template.
    success_url = '...'  # Replace with your URL or reverse().

    def post(self, request, *args, **kwargs):
        form_class = self.get_form_class()
        form = self.get_form(form_class)
        files = request.FILES.getlist('file_field')
        if form.is_valid():
            for f in files:
                ...  # Do something with each file.
            return self.form_valid(form)
        else:
            return self.form_invalid(form)
```

## Penanganan Unggah

When a user uploads a file, Django passes off the file data to an *upload
handler* -- a small class that handles file data as it gets uploaded. Upload
handlers are initially defined in the [`FILE_UPLOAD_HANDLERS`](/id/2.1/ref/settings/#std-setting-FILE_UPLOAD_HANDLERS) setting,
which defaults to:

```
["django.core.files.uploadhandler.MemoryFileUploadHandler",
 "django.core.files.uploadhandler.TemporaryFileUploadHandler"]
```

Together [`MemoryFileUploadHandler`](/id/2.1/ref/files/uploads/#django.core.files.uploadhandler.MemoryFileUploadHandler) and
[`TemporaryFileUploadHandler`](/id/2.1/ref/files/uploads/#django.core.files.uploadhandler.TemporaryFileUploadHandler) provide Django's default file upload
behavior of reading small files into memory and large ones onto disk.

You can write custom handlers that customize how Django handles files. You
could, for example, use custom handlers to enforce user-level quotas, compress
data on the fly, render progress bars, and even send data to another storage
location directly without storing it locally. See [Menulis penangan unggah penyesuaian](/id/2.1/ref/files/uploads/#custom-upload-handlers)
for details on how you can customize or completely replace upload behavior.

### Dimana data terunggah disimpan

Sebelum anda menyimpan berkas terunggah, data butuh disimpan di suatu tempat.

By default, if an uploaded file is smaller than 2.5 megabytes, Django will hold
the entire contents of the upload in memory. This means that saving the file
involves only a read from memory and a write to disk and thus is very fast.

Bagaimanapun, jika sebuah berkas terunggah terlalu besar, Django akan menulis berkas terunggah ke berkas sementara disimpan di sistem direktori sementara. Pada serambi seperti-Unix ini berarti anda dapat mengharap Django membangkitkan sebuah berkas dipanggil seperti sesuatu `/tmp/tmpzfp6I6.upload`. Jika sebuah unggahan cukup besar, anda dapat melihat berkas ini tumbuh dalam ukuran seperti Django mengalirkan data ke cakram.

These specifics -- 2.5 megabytes; `/tmp`; etc. -- are simply "reasonable
defaults" which can be customized as described in the next section.

### Merubah perilaku penanganan unggah

Ada sedikit pengaturan yang mengendalikan perilaku unggah berkas Django. Lihat File Upload Settings 1 untuk rincian.

### Merubah penanganan unggah dengan cepat

Sometimes particular views require different upload behavior. In these cases,
you can override upload handlers on a per-request basis by modifying
`request.upload_handlers`. By default, this list will contain the upload
handlers given by [`FILE_UPLOAD_HANDLERS`](/id/2.1/ref/settings/#std-setting-FILE_UPLOAD_HANDLERS), but you can modify the list
as you would any other list.

For instance, suppose you've written a `ProgressBarUploadHandler` that
provides feedback on upload progress to some sort of AJAX widget. You'd add this
handler to your upload handlers like this:

```
request.upload_handlers.insert(0, ProgressBarUploadHandler(request))
```

You'd probably want to use `list.insert()` in this case (instead of
`append()`) because a progress bar handler would need to run *before* any
other handlers. Remember, the upload handlers are processed in order.

Jika anda ingin mengganti penanganan unggah secara lengkap, anda dapat cukup memberikan daftar baru:

```
request.upload_handlers = [ProgressBarUploadHandler(request)]
```

> **Note**
>
> You can only modify upload handlers *before* accessing
> `request.POST` or `request.FILES` -- it doesn't make sense to
> change upload handlers after upload handling has already
> started. If you try to modify `request.upload_handlers` after
> reading from `request.POST` or `request.FILES` Django will
> throw an error.
>
> Dengan demikian, anda harus selalu merubah penanganan unggahan sedini mungkin dalam tampilan anda.
>
> Juga, `request.POST` diakses oleh [`CsrfViewMiddleware`](/id/2.1/ref/middleware/#django.middleware.csrf.CsrfViewMiddleware) yang diadakan secara awalan. Ini berarti anda akan butuh menggunakan [`csrf_exempt()`](/id/2.1/ref/csrf/#django.views.decorators.csrf.csrf_exempt) pada tampilan anda untuk mengizinkan anda merubah penangan unggahan. Anda kemudian akan butuh menggunakan  [`csrf_protect()`](/id/2.1/ref/csrf/#django.views.decorators.csrf.csrf_protect) pada fungsi yang sebenarnya mengolah permintaan. Catat bahwa ini berarti bahwa penangan mungkin mulai menerima berkas unggahan sebelum CSRF pemeriksaan telah diselesaikan. Kode contoh:
>
> ```
> from django.views.decorators.csrf import csrf_exempt, csrf_protect
>
> @csrf_exempt
> def upload_file_view(request):
>     request.upload_handlers.insert(0, ProgressBarUploadHandler(request))
>     return _upload_file_view(request)
>
> @csrf_protect
> def _upload_file_view(request):
>     ... # Process request
> ```