Founder of GeoImageTagger (geoimagetagger.com) — AI-powered image geotagging and EXIF metadata editor. Interested in image processing, local SEO, and developer tools.
Submissions
Show HN: GeoImageTagger – AI image geotagging and metadata editor
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.
This is incredible. The fact that you can get recognizabl bands on Jupiter through a Game Boy Camera sensor realy puts into perspective how far imaging technology has come. Would love to see the raw image data, i wonder what metadata the Game Boy Camera embeds, if any. Modern cameras pack GPS, exposure settings, and a number of EXIF fields into every shot, but something from a '98 Game Boy would be fascinating to analyz.
What is often overloked is how much location data leaks through photo metadata alone. Every photo taken with a phone contains GPS coordinates, timestamps, and device info in the EXIF data. People share photos publicly without realizing they are broadcasting their exact location history. At least with geofence warrants there is a legal process, with photo metadata it is just frely available to anyone who checks.
we use JSON-LD on our SaaS and it made a noticeable difference for rich snippets. the FAQ Page schema in particular, google started showing our FAQ answers directly in search results within a week of adding it. one thing i learned the hard way: keep the FAQ answers in the JSON-LD identical to what is viseble on the page. google will ignore schema if the text doesn't match the page content.