Google Lens Scraper — Reverse Image Search

What does Google Lens Scraper do?

Reverse image search with Google Lens. Submit an image URL — get back visual matches, exact matches, shopping matches, and related searches.

Why use Google Lens Scraper?

• Visual + exact + shopping matches. Every match type Lens surfaces, tagged visual_match / exact_match / shopping_match.
• Related search chips. Google's suggested follow-up queries, emitted as type: related_search records.
• No Apify image upload needed. Pass a URL — we fetch it.
• Shopping integration. Shopping matches include price, merchant, gpcid (feed into google-products-scraper).
• No CAPTCHAs reach you. Lens's JS challenge is handled by ScrapeBadger's browser farm.

What data can Google Lens Scraper extract?

Field	Type	Description
type	string	visual_match / exact_match / shopping_match / related_search
title	string	Match description
link	string	Source page URL
source	string	Host website
thumbnail	string	Match image URL
price	object	Shopping match: {value, currency, extracted}

How to scrape Google Lens

1. Click Try for free.
2. Paste the image URL (must be publicly reachable).
3. Optional: add a text query to constrain results, set country / language.
4. Toggle visual_matches / exact_matches (default: both on).
5. Click Start — matches stream into the dataset.

How much will it cost?

$0.006 per image (≈ $6 per 1,000 images). One call per image. Shopping + visual + related search chips are all included — no extra credits.

Competitor benchmark

Actor	Author	Price	Notes
zen-studio/google-lens-scraper	zen-studio	~$7.99 / 1k images	Pay-per-event
newyear/google-lens-scraper	newyear	$15 /mo subscription	Deprecated
scrape-badger/google-lens-scraper	ScrapeBadger	$6 / 1k images	25% under zen-studio, no subscription

Input

Configure the run in the Input tab above, or pass a JSON object matching the fields below when calling the Actor via the Apify API.

Field	Required	Description
image_url	✅	Publicly reachable image URL.
query	—	Optional text constraint.
product	—	Pre-narrow to shopping matches.
visual_matches	—	Default true.
exact_matches	—	Default false — slower.
country / language	—	Defaults us / en.

Output

Every successful run streams records into the run's dataset. Download as JSON, CSV, XML, Excel, or HTML from the Dataset tab; consume programmatically via the Apify API or webhooks.

Example record:

[
  {
    "type": "visual_match",
    "title": "Red running shoes \u2014 Nike Pegasus 41",
    "link": "https://example.com/shoes",
    "source": "example.com",
    "thumbnail": "https://encrypted-tbn0.gstatic.com/\u2026"
  },
  {
    "type": "shopping_match",
    "title": "Nike Pegasus 41 Men's",
    "link": "https://nike.com/\u2026",
    "source": "Nike.com",
    "thumbnail": "https://\u2026",
    "price": {
      "value": "$140.00",
      "currency": "USD",
      "extracted": 140.0
    }
  },
  {
    "type": "related_search",
    "title": "Running shoes for marathons"
  }
]

Tips / Advanced options

• Cache your source images. Google's CDN returns 404 if the source URL disappears mid-run. Host on S3 / Cloudflare for reliability.
• Shopping matches ship with gpcid. Pipe them through google-products-scraper for full specs, offers, variants.
• exact_matches is slower. Only enable when you need to track visually identical images across the web (copyright / brand monitoring).
• Related searches are cheap ideation fuel. For SEO content research, related chips often beat autocomplete for breadth.

FAQ, Disclaimers, Support

Does it work with private / auth'd images?

No — Google Lens needs to fetch the image; it must be public.

Can I upload a local file?

Not directly from the Apify input. Host your image on S3 / Cloudflare / imgur and pass the URL.

What's a visual match vs. exact match?

Visual = visually similar (same scene, different angle). Exact = the same image file (copyright / reuse tracking).

How big can the image be?

Google Lens accepts up to ~10 MB per image. Larger images are downscaled server-side.

Disclaimer

This Actor scrapes public Google data only. You're responsible for compliance with Google's Terms of Service and any applicable data-protection laws (GDPR, CCPA, etc.) in your jurisdiction. ScrapeBadger does not store the scraped results — they are delivered directly to your Apify dataset.

Support

Something not working? Open a ticket in the Issues tab above — we triage within one business day. Full API reference: docs.scrapebadger.com.

Related Actors

• google-images-scraper — Text-based image search
• google-products-scraper — Deep product detail from gpcid

Powered by

ScrapeBadger — Google-optimised residential proxy pool + browser-farm fallback, 99.7% uptime, unmetered bandwidth. No CAPTCHAs reach you.