iCloud Image Labeler
Auto-label your Apple Photos library using any OpenAI-compatible LLM. Generates keywords, titles, descriptions, and OCR text for photos and videos, then writes the metadata back into Photos.app.
Works with any OpenAI-compatible API — designed for LM Studio but also works with Ollama, vLLM, or cloud providers.
How It Works
Photos.app ──> Discovery ──> Export ──> LLM ──> Writer ──> Photos.app
(osxphotos) (Pillow) (API) (PhotoScript)
- Discovery — Queries the Photos library for media with no keywords set, filtered by date range and media type. Videos this tool labeled with other frame settings are relabeled too, up to 20 per cycle; while more remain, the next cycle starts right away instead of waiting for the poll interval.
- Export — Exports photos as JPEG (with HEIC/iCloud fallbacks), extracts frames from videos via ffmpeg (evenly spaced, at most 2 per second).
- LLM — Sends images to an OpenAI-compatible API. Returns structured JSON with keywords, title, description, and OCR text. Video frames are sent in batches, and a final text-only request merges the batch results into one set of labels.
- Writer — Writes metadata back into Photos.app via PhotoScript (AppleScript automation).
Photos are processed in parallel (configurable thread count), videos sequentially.
Requirements
- macOS (requires Photos.app and AppleScript)
- Python 3.10+
- ffmpeg (for video frame extraction)
- An OpenAI-compatible LLM API (LM Studio, Ollama, etc.)
Installation
brew tap ziadalzarka/tap
brew install icloud-image-labeler
iCloud Settings
For best performance, go to System Settings → Apple Account → iCloud → Photos and enable Download Originals to this Mac. This downloads all photos in advance so the labeler doesn't have to wait for individual iCloud downloads during processing.
Quick Start
# Interactive setup — connects to your LLM and picks a model
icloud-image-labeler init
# Process all unprocessed media
icloud-image-labeler run
Usage
# Process 5 items from the last 30 days
icloud-image-labeler run --limit 5 --days 30
# Preview without writing (dry run)
icloud-image-labeler run --dry-run
# Photos only, skip videos
icloud-image-labeler run --no-video
# Process media from 60 to 30 days ago
icloud-image-labeler run --days 60 --to-days 30
# Process specific photos by UUID
icloud-image-labeler run --uuid ABC123 DEF456
# Run continuously (daemon-style loop)
icloud-image-labeler run --loop
# Use a specific model or API endpoint
icloud-image-labeler run --base-url http://localhost:1234/v1 --model my-model
# Debug logging
icloud-image-labeler run -v
All run Options
| Flag | Description |
|---|---|
--limit N |
Max items to process |
--days N |
Look back N days (0 = all time) |
--to-days N |
Skip most recent N days |
--photo / --no-photo |
Include/exclude photos |
--video / --no-video |
Include/exclude videos |
--write |
Force write metadata |
--dry-run |
Preview without writing |
--base-url URL |
LLM API endpoint |
--api-key KEY |
API key for LLM |
--model NAME |
Model identifier |
--threads N |
Parallel photo threads |
--video-frames N |
Frames to extract per video |
--video-frame-batch N |
Video frames per LLM request (0 = all in one) |
--uuid UUID [...] |
Process specific photo UUIDs |
--loop |
Run continuously with poll interval |
--reindex |
Reprocess items labeled by a different model, and videos labeled with different frame settings |
-v, --verbose |
Debug logging |
Configuration
Config is stored at ~/.image-labeler/config.json. Run icloud-image-labeler init for interactive setup, or manage directly:
icloud-image-labeler config show # View current config
icloud-image-labeler config set days 14 # Update a value
icloud-image-labeler config reset # Reset to defaults
icloud-image-labeler config path # Print config file path
If no config exists when you run icloud-image-labeler run, the setup wizard launches automatically.
| Key | Default | Description |
|---|---|---|
base_url |
http://localhost:1234/v1 |
OpenAI-compatible API endpoint |
api_key |
"" |
API key (optional, empty for local LM Studio) |
model |
qwen/qwen3.5-9b |
Model identifier |
days |
0 |
Look back N days (0 = all time) |
to_days |
0 |
Skip most recent N days |
limit_per_cycle |
0 |
Items per cycle (0 = all) |
threads |
4 |
Max parallel photo threads |
video_frames |
30 |
Frames to extract from videos |
video_frame_batch |
5 |
Video frames per LLM request (0 = all in one) |
max_dimension |
1024 |
Max image dimension sent to LLM (px) |
photo |
true |
Include photos in processing |
video |
true |
Include videos in processing |
write |
true |
Write metadata to Photos.app |
poll_interval |
300 |
Seconds between cycles in loop/daemon mode |
Daemon
Run as a background service that auto-starts on login via macOS Launch Agent:
icloud-image-labeler daemon start # Install and start Launch Agent
icloud-image-labeler daemon status # Check if running
icloud-image-labeler daemon restart # Apply config changes
icloud-image-labeler daemon stop # Uninstall Launch Agent
The daemon runs as com.image-labeler under ~/Library/LaunchAgents/. It auto-restarts on crash and starts on login. Logs go to ~/.image-labeler/daemon.log.
Metrics
Processing metrics are stored in SQLite at ~/.image-labeler/metrics.db.
icloud-image-labeler metrics serve # Open Datasette UI at http://localhost:8001
icloud-image-labeler metrics serve --port 9000 # Custom port
icloud-image-labeler metrics path # Print database path
Per-item metrics: export/LLM/write durations, image dimensions, LLM retry count, keyword count, OCR presence, error details, and model used.
Per-run metrics: items found/processed/failed, wall-clock duration, model, thread count, and average LLM latency.
Architecture
labeler/
cli.py — argparse CLI (init, run, daemon, config, metrics subcommands)
init.py — interactive first-run setup wizard
config.py — ~/.image-labeler/config.json management
discovery.py — osxphotos query for unprocessed media
exporter.py — photo export (HEIC/iCloud fallbacks), video frame extraction
llm.py — OpenAI-compatible client, JSON parsing, retry logic
processor.py — batch orchestration, parallel photos + sequential videos
writer.py — PhotoScript metadata writes (thread-safe)
metrics.py — SQLite metrics recording
daemon.py — macOS Launch Agent lifecycle
shutdown.py — graceful shutdown (SIGINT/SIGTERM handling)
checks.py — pre-flight dependency checks (ffmpeg, Photos.app)
License
MIT
Metadata
Release files for icloud-image-labeler 0.1.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 | Actions |
|---|---|---|---|---|
| icloud_image_labeler-0.1.4.tar.gz | 33.0 kB | Without provenance | Details for icloud_image_labeler-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| icloud_image_labeler-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for icloud_image_labeler-0.1.4-py3-none-any.whl |
Total release size: 70.1 kB
Release files / icloud_image_labeler-0.1.4.tar.gz
| Download URL | icloud_image_labeler-0.1.4.tar.gz |
|---|---|
| Size | 33.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
81eeeb14245607d1df9d570c1e8392415c47522599fd656d5d821f2f32c63910
|
|
BLAKE2b-256 checksum How to use checksums |
d2794c6e37bd76d046a52edd277b56d9f3da692d2de1d781b5ee9363832a5100
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.14
|
Release files / icloud_image_labeler-0.1.4-py3-none-any.whl
| Download URL | icloud_image_labeler-0.1.4-py3-none-any.whl |
|---|---|
| Size | 37.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e5e8e9d5652f31c2c811d38844a1d45e5ebd5e30e42113466f0da7bba5c98a42
|
|
BLAKE2b-256 checksum How to use checksums |
ba770d3b615a399caf79e53396d101094536e18888ac8a1a80cbd59eb143935b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.14
|
Security for icloud-image-labeler 0.1.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.