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.
tosief•58m ago
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.