How to send multiple forms with Ajax (FormData) in Django

How to send multiple forms with Ajax (FormData) in Django

How to send multiple forms with Ajax (FormData) in Django

In this article, I am going to show you how to send multiple forms in Django using Ajax and FormData. Normally, it’s also possible to send forms only with Ajax by defining data inside the function. However, with FormData it becomes much simpler and faster to handle the form submission.

If you are a beginner, don’t worry we will go step by step through this tutorial. As always let’s create our Django project named mysite then create an app named core.

We are going to use images in our project, so we have to configure in order to serve static and media files and display templates. Update the TEMPLATES configuration like below:

Now, we should add static and media files configurations at the end of

Well done! Next, we need to add models inside I will keep it as simple as possible so, the fields are title, description, and image for now:

Then, we need to migrate our models, so run the following commands in the console to make migrations:

Once it’s completed, open your and we are going to create a very simple blog view just to show created posts for now:

then, we need to define a path in order to display our view in the browser so, update like below:

Next, add a new folder named templates in the root level of the project to store our HTML files and inside it add two files named base.html and blog.html:


You can see two URLs inside the code snippet above one of them is for the blog and the second link is to create posts.


So, the blog template is ready to display all posts and it’s time to add a new function to handle post creation.

FormData and AJAX

FormData is basically a data structure that can be used to store key-value pairs. It’s designed for holding forms data and you can use it with JavaScript to build an object that corresponds to an HTML form. In our case, we will store our form values and pass them into ajax, and then ajax will make a POST request

to Django back-end.

Now, create a new HTML file named create-post.html in the templates directory and add the following code snippet below:


As you can see in the <script> part, first we are creating a FormData object and then using append() method to append a key-value pair to the object. You can change the key name whatever you want but I am keeping it the same as the field names because we will use them later to fetch data in Django views. You can see I am using the field id to get the right fields and the values are fetched by using val() method.

The image is file input so we can’t get the file just using val() method.  The file input stores list of files and since we are uploading only one file, we can get it from the first position of the list.

At the beginning of this tutorial, we said that we want to send multiple forms from a single view, and to achieve that we must define an extra field just to separate  POST requests in the back-end. I created a new key-value pair named action and the value is create-post. Once a POST request has been sent to the views, it will fetch the action field, and if its create-post then a new object will be created. You can add how many forms you want but keep in mind that you have to define an extra field to separate these forms.

Finally, we appended csrfmiddlewaretoken to avoid 403 forbidden when the POST request has been made.

In the ajax function, instead of defining each filed manually, we are passing FormData directly into the data property.

It’s imperative to set the contentType option to false, forcing jQuery not to add a Content-Type header for you, otherwise, the boundary string will be missing from it. Also, you must leave the processData flag set to false, otherwise, jQuery will try to convert your FormData into a string, which will fail. Because we are sending images the enctype must be ‘multipart/form-data’ so our image file will be encoded.

Great! Now, let’s switch to our and fetch all these data in order to create a new post object:

Simply, we are getting the data by its key name and then using in create() method to create a new object in the database. As you see in the if statement we checked the action name, so if the action name is create-post then the object will be created.

Finally, let’s update by adding a new path:

That’s all! Now, you can run the Django server and check the functionality. It will look like below:

Django Server in Action

Django Server in Action

You can get the source code from my GitHub repository below:

About the author

Stay Informed

It's important to keep up
with industry - subscribe!

Stay Informed

Looks good!
Please enter the correct name.
Please enter the correct email.
Looks good!

Related articles


Creating Our Own Chat GPT

In June, OpenAI announced that third-party applications' APIs can be passed into the GPT model, opening up a wide range of possibilities for creating ...


The Ultimate Guide to Pip

Developers may quickly and easily install Python packages from the Python Package Index (PyPI) and other package indexes by using Pip. Pip ...

Building a serverless web application with Python and AWS Lambda

AWS Lambda is a serverless computing solution that enables you to run code without the need for server provisioning or management. It automatically ...


B Easy January 5, 2021 at 11:38 pm

Hello, this is a great article thank you! There is only one problem that I can see with this setup. When using create() to create a model instance none of the validation is run on the model fields. This means if for instance you had an email field and someone entered ‘kljkjkj’ it would still save it. This doesn’t apply to this specific case but in case anyone else sees this it’s something to keep in mind. If you need validation just import django.core.ValidationError and run model.full_clean() to validate the fields, if the validation fails you can delete the object and return the message_dict to the front end to display the errors to the user. Again, this doesn’t apply here because it doesn’t look like this needs validation but a different type of model could. Thanks again!

B Easy January 5, 2021 at 11:56 pm

disregard the last of my comments, I wasn’t thinking. The input would validate that it’s an email before letting you submit it. smh I need a break

Sign in

Forgot password?

Or use a social network account


By Signing In \ Signing Up, you agree to our privacy policy

Password recovery

You can also try to

Or use a social network account


By Signing In \ Signing Up, you agree to our privacy policy