charmfix
Repair the EXIF metadata of Kodak Charmera photos so Apple Photos, and everything else, shows the right date, size and camera. Only metadata changes: every byte of image data stays the same (→ REPAIRS.md), and charmfix checks this before it writes each file (→ REPAIRS.md). Source files are never modified (→ CLI.md). Repaired copies go to a separate folder.
What is wrong with Charmera files
The Charmera uses a Generalplus chip; its JPEGs carry a GPEncoder comment. Most files have no
EXIF at all, so Photos falls back to the import or copy date. Other firmware writes broken EXIF:
dates like 2026:03:03:12:16:29, a 640×480 size on a 1440×1080 image, or a MakerNote that points
outside the EXIF block. charmfix fixes all of these; the exact rules are in
REPAIRS.md.
Install
Released versions are published to PyPI. With uv:
uv tool install charmfix # puts `charmfix` on your PATH
uvx charmfix -h # or run it without installing
pipx install charmfix works too. Before the first release, or to run unreleased changes, install
from a checkout of this repository (→ DEVELOPMENT.md):
uv tool install .
uvx --from . charmfix -h
Supported Python versions → DEVELOPMENT.md.
Usage
charmfix /Volumes/CHARMERA # writes to ~/Pictures/Kodak Charmera Repaired
charmfix /Volumes/CHARMERA -o ~/Desktop/fixed --report ~/Desktop/charmfix-report.json
charmfix /Volumes/CHARMERA --dry-run -v # show what would change, write nothing
Without -o, copies go to the default output folder → CLI.md. All options, exit
codes and the report format are in CLI.md. Each file gets a status →
REPAIRS.md. Running charmfix again on the same card skips files it has already
written → CLI.md.
Run it on the card itself. When a file has no usable EXIF date (often no EXIF at all), the
capture date is the file's modification time, which the camera sets when it takes the photo
(rule 1a). Use the mounted card, or a copy that kept the times (cp -p, Finder
copy). Downloaded or exported files usually carry the copy time instead.
macOS blocks the card? Follow the hint charmfix prints (→ CLI.md): allow the app you run it from under System Settings → Privacy & Security → Files and Folders → Removable Volumes (or Full Disk Access), then restart that app.
Apple Photos workflow
- Insert the card and run
charmfix /Volumes/<card> --report ~/charmfix-report.json. - Check the summary and look at any
partialorfailedlines. - In Photos, choose File → Import… and pick the output folder.
Documentation
| Location | Audience | Authority |
|---|---|---|
| CLI.md | Users, developers and AI agents | Canonical contract |
| REPAIRS.md, DEVELOPMENT.md, TESTING.md | Developers and AI agents | Canonical contracts |
| AGENTS.md, CLAUDE.md (imports AGENTS.md) | AI agents | How to use the contracts |
README.md |
Users | Non-canonical user guide |
License
MIT → LICENSE.
Metadata
Release files for charmfix 0.1.0
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 | Actions |
|---|---|---|---|---|
| charmfix-0.1.0.tar.gz | 26.0 kB | With provenance | Details for charmfix-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| charmfix-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for charmfix-0.1.0-py3-none-any.whl |
Total release size: 56.7 kB
Release files / charmfix-0.1.0.tar.gz
| Download URL | charmfix-0.1.0.tar.gz |
|---|---|
| Size | 26.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8b94b14c7672bd924bd456b2995b07576210b468cd2a2216ef74c1c2fde7f20b
|
|
BLAKE2b-256 checksum How to use checksums |
689c3e6b749392916dd20841c5614ac468077f3452077ba2c5c5194fb8e7dac8
|
| 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 Nov 7, 2026.
Transparency logRelease files / charmfix-0.1.0-py3-none-any.whl
| Download URL | charmfix-0.1.0-py3-none-any.whl |
|---|---|
| Size | 30.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3817653dcc07657f3368d787cf8f028d374fc33c356d24108d89781df459605d
|
|
BLAKE2b-256 checksum How to use checksums |
8c9d80a7fffa2cae8d70e133061becec82992731596fe52a9df58f01f5c8bf8d
|
| 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 Nov 7, 2026.
Transparency logSecurity for charmfix 0.1.0
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
Both files in this release have been uploaded with provenance metadata.
Attestation for charmfix-0.1.0.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 Nov 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.