django-import-export
Introduction
Straightforward, reliable and comprehensive file import / export for your Django application.
django-import-export is an application and library which lets you manage import / export from / to a variety of sources (csv, xlsx, json etc).
Can be run programmatically, or with optional integration with the Django Admin site:
Features
Import / export via Admin UI Integration or programmatically
Import to and from a variety of file formats (csv, json, xlsx, pandas, HTML, YAML… and anything else that tablib supports)
Preview data before importing in Admin UI
Support for bulk import
Flexible handling of foreign key relationships
Many-to-many relationship support
Validation of imported data
Define custom transformations for exported data
Import / export the same model instance as different views
Export using natural keys for portability between environments
Select items for export via the Admin UI object list
Select fields for export via the export form
Use django permissions to control import / export authorization
Internationalization support
Based on tablib
Support for MySQL / PostgreSQL / SQLite
Extensible - add custom logic to control import / export
Handle import from various character encodings
Celery integration
Test locally with Docker
Comprehensive documentation
test coverage :100:
Supports dark mode :rocket:
Example use-cases
django-import-export is designed to be extensible and can be used to support a variety of operations. Here are some examples of how it has been used in the wild:
Configure external cron jobs to run an import or export at set times
Use permissions to define a subset of users able to import and export project data
Safely update project reference data by importing from version controlled csv
Create portable data to transfer between environments using natural keys
Manage user access to an application by importing externally version controlled auth user lists
Add hooks to anonymize data on export
Modify import / export UI forms to add dynamic filtering on import / export.
Build a migration layer between platforms, for example take a Wordpress export and import to Wagtail
Getting started
Help and support
Commercial support
Commercial support is provided by Bellaport Systems Ltd
Releases
4 maintainers
Metadata
4 maintainers
Release files for django-import-export 4.4.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django_import_export-4.4.4.tar.gz | 2.3 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_import_export-4.4.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.4 MB
Release files / django_import_export-4.4.4.tar.gz
| Download URL | django_import_export-4.4.4.tar.gz |
|---|---|
| Size | 2.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
632d965c05363d2ee1c829f99b4a5e58cf7bf0d5899d74f53f5a1310dd7ecd45
|
|
BLAKE2b-256 checksum How to use checksums |
0f566cea22f18c0dd27fa632e904e88f4e1f3108ae2a35e298ab80dc8afa1279
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / django_import_export-4.4.4-py3-none-any.whl
| Download URL | django_import_export-4.4.4-py3-none-any.whl |
|---|---|
| Size | 158.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cba85e6fd5fc4b6f09bdcc6144e3f3cdc05b5f3874f7d67137e234675374e763
|
|
BLAKE2b-256 checksum How to use checksums |
17d1727ee8b941e1523866c91fa48f8563d75963c4799fc72d7bfbb34eb917fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logSecurity for django-import-export 4.4.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for django_import_export-4.4.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
