I built GeoImageTagger after getting frustrated with how many separate tools it takes to manage image metadata.
Photographers and local businesses often need three or four different tools just to geotag photos, edit EXIF/IPTC/XMP metadata, and optimize the final images. I wanted one browser-based tool that could handle the whole workflow.
It’s built with Next.js, the Google Gemini API, Leaflet, and the browser’s Canvas API.
A few decisions I made:
* All image processing happens client-side, so images never leave the browser.
* EXIF, IPTC, and XMP metadata are written directly into the image file.
* AI can generate tags, titles, and descriptions based on the image.
* There are eight free tools, and the image-procesing features don’t depend on a backend.
I’d appreciate any feedback, especially on the decision to keep the processing entirely client-side.
I like that everything runs client-side. That's a thoughtful choice for a tool dealing with image metadata and privacy. Curious how it performs with larger photo collections.
Consolidating geotagging and metadata editing into one tool is a nice idea. Fewer context switches is always a plus, especially for photographers managing lots of images.
The all-in-one approach is compelling. Keeping the processing in the browser instead of relying on a backend is a nice touch, especially for anyone working with sensitive location data.
Nice to see a desktop-first option for this workflow. A lot of photo metadata tools are either overkill or spread across multiple apps, so this feels refreshingly focused.
Keeping everything in the browser is a smart choice, especially for location-sensitive photos.
I’d be curious how well the metadata survives after compression or format conversion.
This feels especially useful for anyone cleaning up travel or property photos before sharing them.
The offline, client-side approach makes the privacy angle much more convincing.
The browser-based approach makes this feel lightweight without compromising privacy.
Would love to see how it performs with large photo batches and RAW files.
A browser-based tool like this could save a lot of time for photographers and content teams.
The fact that the files stay on the device makes it much easier to trust.
The map-based editing makes this much more intuitive than digging through raw EXIF fields.
Keeping the whole process local is a smart touch for anyone handling sensitive photo data.
Love that the core editing happens entirely in the browser instead of sending files to a server.
That makes it feel much safer for photos carrying sensitive location data.
This could save a lot of time for people organizing travel shoots or fieldwork photos.
Being able to edit GPS data without sending files to a server is a big plus.
26 comments
[ 3.7 ms ] story [ 29.6 ms ] threadI built GeoImageTagger after getting frustrated with how many separate tools it takes to manage image metadata.
Photographers and local businesses often need three or four different tools just to geotag photos, edit EXIF/IPTC/XMP metadata, and optimize the final images. I wanted one browser-based tool that could handle the whole workflow.
It’s built with Next.js, the Google Gemini API, Leaflet, and the browser’s Canvas API.
A few decisions I made:
* All image processing happens client-side, so images never leave the browser. * EXIF, IPTC, and XMP metadata are written directly into the image file. * AI can generate tags, titles, and descriptions based on the image. * There are eight free tools, and the image-procesing features don’t depend on a backend.
I’d appreciate any feedback, especially on the decision to keep the processing entirely client-side.