Gadget Daily News

Search
Photography Google Photos Checked October 2026

Why is Google Photos showing the wrong date, and how to fix it

Find where the bad date came from, then use the right fix: bulk edits on photos.google.com for small batches, or a file fix before upload for big archives.

Question: My old photos all landed on the day I uploaded them. How do I fix the dates in bulk?
Answer: Google Photos shows the wrong date because it trusts the date stored inside the file, and many files carry a bad one or none at all. Scans hold the day you scanned them, WhatsApp pictures carry only the day they were saved, and some cameras write a wrong GPS time that Google Photos can pick up instead. You can fix any of them with Edit date & time on photos.google.com, but that fix lives only in Google Photos, so for big archives it's better to fix the files before you upload.

Where Google Photos gets the date

Google Photos sorts your library by capture date, which it reads from the photo’s own metadata. When that date is missing, it appears to fall back on another timestamp, such as the day you uploaded it. Google doesn’t publish the exact order. That’s how Google Photos Community volunteers explain it in the threads below, and it’s why an old print can turn up under today’s date.

There are several places a date can hide inside a photo, and they don’t always agree.

Date field Where it comes from Common way it goes wrong
EXIF DateTimeOriginal The camera or phone at the moment of capture Camera clock never set, or set to the wrong time zone
GPS date and time stamp The camera’s GPS receiver A buggy camera writes a wrong date, and Google Photos can use it as the date taken
File created or modified date The computer or phone that saved the file Changes every time the file is copied, restored or downloaded
Takeout .json sidecar (photoTakenTime) Google’s own database, exported next to the photo Lost when the .json files are deleted or ignored
Upload date The day the file reached Google Photos Used when nothing else is there

On a scanned print, the “capture” date is the moment the scanner created the file. In a 2018 Community thread, one user’s scans of 1997 prints all showed up under 2018, the year they were scanned and uploaded.

Work out where the bad photos came from

The fastest way to the right fix is to find the source, because each one breaks the date differently. Open one of the wrong photos on photos.google.com and click the Info button (the “i”) to see the details panel. On the phone app, open the photo and swipe up.

Look at three things: the file name, the camera model (if any), and the time zone shown next to the date. A name like IMG-20210314-WA0007.jpg is a WhatsApp file. A name with no camera model and a scan date points to a scanner or PhotoScan. A real camera model with a date years out points to a clock or GPS problem.

Five sources of wrong dates, five different fixes Diagram matching where a photo came from to the fix: scans need a date set per batch, WhatsApp photos take the date from the file name, camera photos stuck on one odd date need the GPS date removed, photos a few hours off need a time zone shift, and Takeout files need their .json dates merged back. Five sources of wrong dates, five different fixes Diagram: find the source, then use its fix Scanned prints Set one date per batch WhatsApp files Date from the file name One odd date Remove the GPS date Hours out Shift the time zone Takeout files Merge the .json dates
Source: Edit your photos, Google Photos Help; All photos uploading to the same date, Google Photos Community, checked October 2026. Note: a diagram of steps, not data.

Scanned prints and slides

Scans land on the scan date because that’s the only date the file has. PhotoScan, Google’s free scanning app, launched in November 2016 and saves scans to Google Photos in one tap, so a weekend of scanning puts hundreds of prints on that one weekend.

For a few albums, fix them inside Google Photos. Group the scans by event or year, select a group on photos.google.com, and choose Set one date & time. If you know the order, pick Shift dates & times instead, set the right date on the first photo, and the rest keep their spacing.

For thousands of scans, fix the files first. One user in a 2018 Community thread had redated thousands of PhotoScan images in Google Photos, then found many had reverted to the scan date months later. The reply explained that the edited date never goes into the file itself. If the date is written into the file before upload, Google Photos reads it, and so does every other app.

The free command-line tool ExifTool can write dates into a whole folder at once, and the commands below use it. Photo managers such as Lightroom Classic can also change capture times, as long as you save the change to the files. If you already use Lightroom, that fits into the import and export routine in our Lightroom Classic workflow for beginners.

WhatsApp and other chat-app photos

WhatsApp pictures show the wrong date because they carry no capture date at all. A Google Photos Community volunteer explained it in November 2025: WhatsApp images have no capture metadata, only file dates, and those change when the files are copied to a new phone. That’s why restoring chats on a new phone can pile years of pictures onto the restore day.

The real date often survives in the file name. WhatsApp usually saves a picture as IMG-20210314-WA0007.jpg: 20210314 is the day WhatsApp saved it, and 0007 counts the files saved that day rather than a time.

You can’t make Google Photos read the name, so write the date into the files before uploading. With ExifTool on a Mac or Linux computer, this sets each photo to noon on the date in its name:

exiftool -overwrite_original '-AllDates<${filename;m/(\d{8})/;$_=$1} 12:00:00' /path/to/WhatsApp/Images

The added time matters. ExifTool’s FAQ says EXIF dates need all six date and time fields, so its plain -alldates<filename trick won’t work on a name that holds only a date and a counter. Noon also keeps clear of Google Photos’ 4 AM rule, which sorts earlier photos into the previous day. Delete the old copies from Google Photos first, or you’ll end up with duplicates.

If the WhatsApp folder is already backed up and you only have a few dozen, editing them by hand on the web is quicker.

Camera photos stuck on one strange date

When every photo from one camera lands on the same wrong day, suspect the GPS date. In an April 2025 Community thread, a user uploaded a batch from a camera, and every photo landed on July 5, 2013 at 8:11 am. The correct date was in the file. A volunteer found the GPS section held a wrong date, and Google Photos used it as the date taken. Removing the GPS section fixed the upload.

That’s why the same file can show the right date in other apps and still land on the wrong day in Google Photos. The volunteer stripped the whole GPS section. If you’d rather keep your location, try removing just the two GPS time tags before uploading, then test one photo:

exiftool -gpsdatestamp= -gpstimestamp= *.JPG

That leaves your location and the camera’s own capture date alone. If the photo still lands on the odd date, remove the whole GPS group with exiftool -gps:all= *.JPG. Check the camera for a firmware update, or turn off its GPS stamping, so the next batch doesn’t need the same fix.

Photos a few hours off, or in the wrong order

A date that’s out by a few hours is almost always a time zone problem. A 2019 Community answer lists the usual causes: mixing cameras with and without GPS, and photos with no time zone in the file, which get the zone of the place they were uploaded from. Mix a GPS phone and a camera without GPS on one trip, and the two sets drift apart by the time difference.

The bulk fix is on the web. Select the photos with the wrong zone, choose Edit date & time, then Shift dates & times, and pick the right time zone before saving.

The answer’s author adds a caution worth repeating: shifting the zone alone may not fix the order, so check the result and adjust the time as well if needed. If only a handful are wrong, editing those few by hand is faster.

Remember the 4 AM rule, too. Photos taken between midnight and 4 AM appear under the previous day, by design.

Takeout downloads and photos moved to a new account

Photos exported with Google Takeout often lose their dates the moment they leave Google, because the date sits in a separate .json file. Each photo comes with a sidecar holding photoTakenTime, plus any date you edited in Google Photos. A Google Photos Community expert explained back in 2019 that date changes made in Google Photos are kept in Google’s database, not in the photo. Delete the .json files, or import the photos into another app without them, and that date is gone.

The sidecar names vary. Older exports used IMG_1234.jpg.json. A 2025 bug report on the free Google Photos Takeout Helper project lists newer names like IMG_1234.jpg.supplemental-metadata.json, some cut short. With ExifTool, match the name your export uses:

exiftool -r -d %s -tagsfromfile "%d%f.%e.supplemental-metadata.json" "-DateTimeOriginal<PhotoTakenTimeTimestamp" -overwrite_original -ext jpg /path/to/Takeout

Swap .supplemental-metadata.json for .json if that’s what your files end in. The timestamp is in UTC, so ExifTool writes it in your computer’s local time zone. ExifTool names the tag after the keys inside the JSON file, so PhotoTakenTimeTimestamp comes from Google’s photoTakenTime field. Keep the .json files until the dates are in the photos.

Fix a batch on photos.google.com

For most people with a few hundred bad dates, Google’s own tool is enough. These are the steps from Google’s help page, as of October 2026:

  1. Go to photos.google.com on a computer.
  2. Hover over a photo and click the check mark to select it. To grab a long run, a tip from a Community answer is to hold Shift and click the last photo’s check mark.
  3. Click More (three dots) at the top, then Edit date & time.
  4. Choose Shift dates & times to set the first photo and move the rest by the same amount, or Set one date & time to give them all one date.
  5. Follow the on-screen steps and save.

Google’s Android steps cover one photo at a time: open it, tap More and then About (or swipe up), tap Edit next to the date, and save. Google notes this works only for backed-up photos.

What a Google Photos date edit doesn’t do

A date fixed in Google Photos doesn’t travel with the photo. Google’s help page says so directly: the edited date shows in Google Photos, “but if you share the photo to other apps or download it, the photo may show the original date and time saved by your camera.”

So don’t spend a weekend redating 5,000 scans in the browser if you plan to move them elsewhere. A download, a move to Apple Photos or a NAS, or a Takeout export without the .json files will bring the wrong dates back. For a large archive, fix the files once, delete the bad copies from Google Photos, and upload the fixed ones. If two cameras disagree by a few minutes, line them up before upload too. Our Lightroom wedding workflow covers syncing camera clocks for exactly this reason.

What to do next

  1. Open one wrong photo on photos.google.com, click Info, and note the file name, camera and time zone.
  2. Match it to a source above: scan, WhatsApp, GPS date, time zone or Takeout.
  3. Under a few hundred photos and staying in Google Photos? Use Edit date & time with Shift dates & times on the web.
  4. A big archive, or files you’ll move later? Fix the dates in the files with ExifTool or Lightroom Classic, delete the bad copies, and re-upload.
  5. Set your camera’s clock and time zone now, and turn off GPS stamping if its dates are wrong.

Sources

More from Gadget Daily News