Local Image Editor
A fast, privacy-friendly image overlay editor. Add a predefined overlay or any custom PNG, JPEG, WebP, or SVG image to a local image, then download the result at its original resolution.
Transparent PNG and SVG files retain their alpha channel while editing and when downloading a PNG. JPEG downloads are flattened because JPEG does not support transparency.
All image processing occurs in the browser. This project has no backend, database, image upload endpoint, or credentials.
Run locally
Requirements: Node.js 22 or newer and npm.
npm install
npm run dev
Open the URL printed by Vite. To create a production build:
npm run build
Docker
Create an optional local .env from the public example and set a host port if needed:
cp .env.example .env
docker compose up --build
The application is served at http://localhost:8080 unless APP_PORT is set. The production image uses nginx and can sit behind a standard reverse proxy.
Compose mounts OVERLAYS_DIR read-only at /usr/share/nginx/html/overlays in the container. It defaults to ./public/overlays, but a deployment can point it at any host directory:
OVERLAYS_DIR=/srv/local-image-editor/overlays
Add or replace images and edit overlays.json in that mounted directory without rebuilding or restarting the application container. Reload the browser after changing overlays.json; it is served without browser caching.
Overlay library
Predefined overlays are loaded at runtime from public/overlays/overlays.json. In Docker deployments, this is the directory configured by OVERLAYS_DIR. To add one, place the image there and add its identifier, label, and filename to overlays.json. No Vue source changes or image rebuild are needed.
{
"id": "example-badge",
"name": "Example badge",
"file": "example-badge.png"
}
Configuration and security
.env is deliberately ignored by Git and Docker builds. .env.example contains only public values. Any variable prefixed VITE_ is embedded into browser JavaScript and must never contain a secret.