Livescraper
Sign inGet Started
Google Maps Photos Scraper

Every photo on a place,
not just the first one.

The Google Maps Scraper hands you one image per place - photo_url, plus a photos_count telling you how many more exist. This is the tool that gets you the rest. Point it at the places you care about and collect their photos as rows.

Start free See pricing
one-time 500 free rows$0.002 per row afterCSV · JSON · ExcelGDPR-aligned
How it works

Places in,
photo links out.

Same entry point as the rest of the Maps toolkit: you name the places, and the job returns what's attached to them.

  1. STEP 1Sign in to the platform.
  2. STEP 2Open the Google Maps Photos Scraper.
  3. STEP 3Add the places, or paste their place IDs.
  4. STEP 4Set the run parameters offered for the job.
  5. STEP 5Choose your output format (CSV / JSON / XLSX).
  6. STEP 6Click Get Data.

Each row is tagged with the place it belongs to, so a run across a whole footprint still reconciles back to your input list.

Why teams use it

Photos are the part
nobody audits.

Past the single hero image

A place page can hold dozens of photos. Most datasets carry one. If the image a customer actually judges you on is the fourth one, you've never looked at it.

Auditable across a footprint

Checking photos by hand works for one location. For fifty it doesn't happen at all - which is why stale, dark or plain wrong images sit on listings for years.

Same place IDs as the rest

Feed in the identifiers you already hold from a Maps run. The photo rows join straight back onto your existing place table.

What you get back

Links to images,
not the images.

This is the distinction worth being clear about up front. What comes back are the photo links Google publishes for a place - the same kind of value the Maps Scraper's photo_url field carries, described in our data dictionary as a "link to the image of the place". Not image files in a zip.

For most work that's what you want: links are small, they join cleanly onto a place table, and you can fetch or render only the ones you actually need. If your workflow requires local copies, downloading from the links is a step you control - which also keeps the licensing question in your hands rather than ours. More on that below.

query
The place you submitted, echoed back on every one of its photo rows.
name
The place's name on Google Maps. Filled when you submit a name or a search; empty when you submit an ID, because the name comes from the search response rather than the photo feed.
google_id
Google's feature ID for the place - the 0x…:0x… pair the photo feed is keyed on.
place_id
Google's Place ID (ChIJ…) - your join key onto a place table you already hold.
location_link
The Google Maps URL for the place, including its coordinates.
photo_id
Google's identifier for this individual photo - use it to de-duplicate across runs.
photo_url
The link to the photo. This is the row: one link per row, not one row per place.
photo_url_big
The same photo at up to 2048×2048, for when the default size is too small to judge detail.
latitude
Latitude of the place the photo belongs to.
longitude
Longitude of the place the photo belongs to.
photo_date
When the photo was posted.
photo_upload_source
Which Google app posted it and how - gmm_android, gmm_ios, and the _review_post / _photo_post variants that tell you whether it arrived attached to a review.
photo_source_video
A video link when the entry is a video rather than a still. Empty on most rows: videos are a small share of any gallery.
photo_tags
Google's own gallery tags for the photo - front, food, vibe - the same tabs you see on the listing.
photo_tag_ids
The numeric IDs behind those tags, for filtering without string matching.
original_photo_url
The thumbnail-sized variant of the photo, as served in the gallery grid.

16 columns per photo - every column above on every plan, including the free tier.

Three identifiers - place_id, google_id and photo_id - make the export joinable onto place data you already hold and de-duplicable across repeat runs, so the photos become an extra table rather than a parallel copy of your place list. Expect many rows per place: a single well-photographed business can produce dozens, so the row count is driven by photo volume rather than by how many places you submitted.

Try 500 rows free
Worth understanding

What the Maps Scraper
already gives you.

Before adding a second tool to your pipeline, it's worth knowing exactly where the first one stops.

The Google Maps Scraper already returns four image-related fields on every place row: photo_url, a link to one image; photos_count, how many the place has in total; logo_url; and street_view. For a lot of jobs that's sufficient - if you only need a thumbnail per row, you already have it.

Where it stops is breadth. A photos_count of 60 tells you there are 59 images you can't see. That gap matters when the question is what does this place actually look like rather than does it have a picture - auditing a franchise, comparing storefronts, or checking whether the images representing you are the ones you'd choose.

So the honest rule of thumb: start with the Maps Scraper. Add this when photos_count is the number you keep wanting to open.

About the Maps Scraper
livescraper.app · which tool
The Maps Scraper gives one thumbnail per place✓
The Maps Scraper gives the photo count✓
The Maps Scraper gives logo and street view links✓
This tool gives every remaining photo✓
Add the second tool only when the count is the answer you need.
Common workflows

Three jobs people
most often run here.

A few examples of how teams use Maps photo data.

Operations

Audit your own listings visually

Pull the photos across every location you own and review them as a sheet. Refurbished sites still showing the old fit-out, seasonal decorations two years out of date, and images of a business that used to occupy the unit all turn up this way.

Operations · Brand
Competitive

Compare storefronts in a market

Photos are the first thing a customer sees in local results. Collecting them across a category and city shows you how you present next to the alternatives - often less flatteringly than anyone internally assumed.

Marketing
Research

Assess sites without visiting

For property, retail or field teams evaluating locations at distance, user-uploaded photos show the actual condition of a frontage, car park or interior - the things a listing description and a single hero shot both quietly omit.

Real estate · Research
Get started
Pricing

Pay only for the rows
you actually pull.

No subscription, no minimum. Your first 500 rows are on us - after that, pay-as-you-go.

Free tier

500 free rows - $0

Every new account, one-time. No credit card required. All scrapers unlocked, full feature set - enough to audit a handful of locations before committing.

$0 forever
Pay-as-you-go

$0.002 per row, after the free tier

Roughly $2 per 1,000 rows. The pre-flight estimator shows the count and credit cost before a run starts - worth checking here, since a place with 200 photos is 200 rows.

Most popular
Enterprise

Custom · large footprints

Volume pricing, SLAs, dedicated workers and bespoke onboarding for recurring audits across hundreds of locations. Tell us your numbers and we'll quote.

Talk to us
Start free See full pricing
10% off your first paid run.Use code LIVESCRAPER10 at checkout.
Sign up
Pairs well with

Find the places,
then look at them.

Photos are an add-on to a place list, not a starting point.

Google Maps Scraper

Where the place IDs come from - every business in a category and city, with photo_url and photos_count already on each row.

Explore

Google Reviews Scraper

The other half of a listing audit. Guests describe in words what the photos show - and reviews often name the thing the images are hiding.

Explore
The legal bit

Photos need more care
than text.

Collecting public links is one thing. Republishing an image is a different question, and we'd rather say so plainly.

The links themselves are public: Google shows them to anyone viewing a place, signed in or not, and collecting publicly visible references for research and auditing is long-established practice. As long as the data is publicly available and the process doesn't disrupt the site, there are no federal laws prohibiting it.

The part that differs from reviews is copyright. A photo on a Maps listing is usually owned by whoever took it - a customer, the business, or a contributor - and a link to an image grants you no licence to reuse it. Auditing your own locations, comparing storefronts internally, or assessing a site are ordinary uses. Republishing someone's photo on your website or in an advert, or using scraped images to train a model you distribute, are decisions with real IP exposure. Those calls are yours, and we'd rather flag them than let a marketing page imply otherwise.

Google's terms also restrict automated access, so this is a terms question as well. We touch nothing behind a login, run no third-party trackers on the data layer, and your exports auto-delete after 30 days.

Sign up now
livescraper.app · use vs reuse
Auditing your own listings is ordinary use✓
Internal competitive review is ordinary use✓
Assessing a site remotely is ordinary use✓
Republishing an image is your call, not ours!
Training a distributed model is your call!
A link is not a licence. Check before you reuse.
Common questions

Things people
ask before signing up.

The questions we hear most. Anything else? Talk to us - humans, not bots, write the answers.

How do I scrape photos from Google Maps?+
Using the Google Maps Photos Scraper:
  1. Sign in to the platform.
  2. Open the Google Maps Photos Scraper.
  3. Add the places, or paste their place IDs.
  4. Set the run parameters offered for the job.
  5. Choose your output format (CSV / JSON / XLSX).
  6. Click Get Data.
Do I get image files or links?+
Links. The output carries the photo references Google publishes for a place - the same kind of value the Maps Scraper's photo_url field holds, which our data dictionary describes as a "link to the image of the place". If you need local copies, downloading from those links is a step you run yourself, which also keeps any licensing decision on your side.
Doesn't the Google Maps Scraper already return photos?+
It returns one - photo_url - plus photos_count, logo_url and street_view. If a thumbnail per place is all you need, use that and skip this entirely. This tool is for when photos_count says 60 and you need more than the first.
Can I use the photos on my own site?+
That's a copyright question, not a scraping one, and the answer is usually no without permission. Photos on a Maps listing generally belong to whoever took them, and having a link grants no licence to republish. Auditing, comparing and assessing internally are ordinary uses; putting someone's photo in your advertising is not. See the section above - we'd rather be direct about this.
How many rows will a run produce?+
It depends entirely on the places. A place with 200 photos can produce far more rows than a place with three, so the pre-flight estimator is worth reading here more than on most tools. Start with a small free-tier run against a representative location to calibrate.
Can I use the same place IDs from a Maps run?+
Yes - that's the intended workflow. Pull your place list with the Google Maps Scraper, then feed those identifiers here so the photo rows join straight back onto your existing table.
How much does it cost?+
The first 500 rows on a new account are free and one-time; after that it's $0.002 per row, pay-as-you-go with no subscription. See pricing for volume rates.

See what your listings actually show.

500 one-time free rows on every new account - no expiry. After that it's $0.002 per row, pay-as-you-go - no card on file until you say so.

Start free See full pricing
Activates instantly · no card required

Scrape photos from Google Maps places

Livescraper's Google Maps Photos Scraper collects the photo links published on a place's Maps listing. You add the places or paste the place IDs you already hold, pick an output format, and download the result as CSV, JSON or Excel - each row tagged with the place it belongs to.

It's worth being clear about what arrives: links to images, not image files. That's the same kind of value the Google Maps Scraper's photo_url field carries, which our data dictionary describes as a link to the image of the place. Links are small, they join cleanly onto an existing place table, and you fetch only the ones you actually need - which also leaves any licensing decision in your hands.

The reason a separate tool exists is breadth. A standard Maps run already gives you photo_url, photos_count, logo_url and street_view on every row. If a thumbnail per place is enough, that's the tool to use. But a photos_count of 60 means 59 images you cannot see, and that gap matters when the question is what a place actually looks like rather than whether it has a picture.

Operations teams audit their own footprint and find refurbished sites still showing an old fit-out. Marketing teams compare storefront imagery across a category, since photos are the first thing a customer sees in local results. Property and field teams assess frontages, car parks and interiors without a site visit. One caveat throughout: a link is not a licence, and photos on a listing generally belong to whoever took them. Start free - your first 500 rows cost nothing and need no credit card.