I wouldn't store binary data like an image in a session, especially if you have a DB-backed session system.
I would instead use a separate model just for the images so that they can be created on the fly by dropzone via an API call, and then you can save the ID of the image object in the session (or update a hidden field in the form) and later attach it to the object you are creating via the form by a foreign key or one-to-one relationship when saving the form object.
There would still be other potential issues like the possibility of orphaned images if a user uploads an image but then doesn't complete the form. You may need some sort of nightly cleanup management command to run to do something with the orphan images, like delete them.
Also, unless you know or manipulate the images to be small, make sure that you don't store them in the database itself, use the file system. The DB is a bad place for binary data blobs in most situations.
-James
I wouldn't store binary data like an image in a session, especially if you have a DB-backed session system.
[....]