django-signature-field
Django field for storing canvas signatures as binary data or image files.
Purpose
Store signature pad output in the database either as a binary blob (default) or as an uploaded PNG file.
Installation
pip install django-signature-field
Quick Start
from django.db import models
from signature import SignatureField
class Contract(models.Model):
title = models.CharField(max_length=100)
# Default: binary storage
signature = SignatureField()
# Or explicitly as blob
signature_blob = SignatureField(field_type="blob")
# Or as image file
signature_image = SignatureField(field_type="image", upload_to="signatures/")
Input formats
The field accepts:
- Raw bytes
- Base64 text
- Data URLs (
data:image/png;base64,...)
Field modes
field_type |
Storage | Django field |
|---|---|---|
"blob" (default) |
Raw PNG bytes in database | BinaryField |
"image" |
PNG file on storage | ImageField |
Development
pip install -e ".[dev]"
pytest
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for django-signature-field 0.1.1
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_signature_field-0.1.1.tar.gz | 191.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_signature_field-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 378.9 kB
Release files / django_signature_field-0.1.1.tar.gz
| Download URL | django_signature_field-0.1.1.tar.gz |
|---|---|
| Size | 191.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
32fb4a10ff92cd66b07b1261e5592a74847dcb55eb47fad059b374550e2e276c
|
|
BLAKE2b-256 checksum How to use checksums |
95b6970172f6e5c7dc70a68fc6bf85b1b2aa7b69dfed9434f4b52f31c0f3c17b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 7, 2026.
Transparency logRelease files / django_signature_field-0.1.1-py3-none-any.whl
| Download URL | django_signature_field-0.1.1-py3-none-any.whl |
|---|---|
| Size | 187.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c8bb2c9bed9a628343768152d9bb4543156878909a7c3de72c7e4314c3022142
|
|
BLAKE2b-256 checksum How to use checksums |
04f16a62b3c77b4bf76dc2fcd77515c7fcf2c6b9ea26d47615bab4ebd79e930b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 7, 2026.
Transparency logSecurity for django-signature-field 0.1.1
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_signature_field-0.1.1.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 Sep 7, 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.
