Facebook Photos Scraper With Engagement Analytics

Facebook Photo Scraper — Reactions, Comments & Shares as JSON

The Facebook Photos Scraper With Engagement Analytics extracts public Facebook photos along with reactionCount, commentCount, shareCount and a derived totalEngagement score for every photo on a page or profile. Add accessibility captions, post captions and owner details, and you get a ready-to-use engagement dataset — no browser, no login, no manual counting. Output ships as clean, structured JSON. Add a page or profile below and run it to see real engagement numbers in minutes.

What is Facebook Photos Scraper With Engagement Analytics?

Facebook Photos Scraper With Engagement Analytics is an Apify Actor that reads the public, logged-out photo viewer Facebook serves to any visitor and turns it into a structured engagement dataset — reaction, comment and share totals per photo, plus captions, owner details, and image URLs. It does not require a Facebook account, login, or session cookies of your own; it warms up its own guest session automatically before requesting data. It's built for social media analysts, brand and competitor monitoring teams, and developers who need photo-level engagement data as JSON rather than scraped HTML or manual screenshots.

What Facebook photo data is publicly available to scrape?

Facebook exposes a photo's image, captions, and aggregate engagement counts to any logged-out visitor; it hides per-type reaction detail and individual identities behind a login.

Data category	Public (logged out)	Restricted (login)
Photo image & permalink	Yes	—
Accessibility (alt) caption	Yes	—
Post caption	Often	Sometimes stripped
Owner/page name	Yes	—
Reaction/comment/share totals	Often	null on some personal photos
Per-reaction-type breakdown	No	Login required
Reactor/commenter identities	No	Login required
Full comment text threads	No	Login required

Facebook Photos Scraper With Engagement Analytics only returns publicly visible data — what any visitor sees, nothing behind a login wall.

What data can I extract with Facebook Photos Scraper With Engagement Analytics?

Every run returns one row per photo, combining identity/media fields with engagement metrics.

Photo identity & media fields

Field	Description
id	Real numeric Facebook photo ID (same value as photoId and facebookId)
photoId	Real numeric Facebook photo ID
facebookId	Numeric Facebook photo ID, duplicated for compatibility with related actors
dataType	Record type marker, always "photo"
image	Direct CDN image URL, when Facebook exposes one
url	Direct permalink to the photo (photo.php?fbid=...)
facebookUrl	Base page/profile URL the photo belongs to
accessibilityCaption	Facebook's own auto-generated alt text describing the image; null if none
caption	Post caption/text attached to the photo; null if none
ownerId	Numeric Facebook ID of the page/profile that owns the photo; null if not resolvable
ownerName	Display name of the page/profile that owns the photo; null if not resolvable
pageAdLibrary	Object echoing the resolved ownerId ({"id": ...}) — kept for schema parity, not actual Ads Library data
inputUrl	The normalized page/profile URL you supplied as input
scrapedAt	ISO-8601 UTC timestamp of when the row was scraped

Engagement metrics

Field	Description
reactionCount	Total reactions on the photo (aggregate only, no per-type split); null when Facebook hides it logged out
commentCount	Total comments on the photo; null when hidden
shareCount	Total shares of the photo; null when hidden
totalEngagement	Derived sum of reactionCount + commentCount + shareCount, using only the components Facebook exposed; null if none are available

🤖 Add-on: Need additional Facebook data?

Want the reaction split behind that aggregate reactionCount? Facebook Comments Scraper: Reaction Breakdown decodes the exact like/love/haha/wow/sad/angry/care totals at the comment level. If you need full post text and computed virality metrics rather than just photos, Facebook Page Posts Scraper With Engagement Analytics covers the whole page feed. For photos and posts inside Facebook Groups instead of pages/profiles, use Facebook Groups Posts & Media Scraper.

How does Facebook Photos Scraper With Engagement Analytics differ from the official Facebook API?

Meta's Graph API requires App Review before it will return Page content, and it does not expose arbitrary public profile or third-party Page photo galleries the way a logged-out browser can see them — Facebook Photos Scraper With Engagement Analytics reads that same logged-out surface directly, without any approval process.

Feature	Facebook Graph API	Facebook Photos Scraper With Engagement Analytics
Approval required	Yes — App Review + Page Public Content Access	No — runs immediately on Apify
Personal profile photos	Not accessible via current public endpoints	Accessible if publicly visible logged out
Third-party Page photos	Only Pages you manage, or via a reviewed public-content feature	Any public page/profile you point it at
Access token / session	Requires a Page access token tied to an authorized app	No token, no login — reads the logged-out surface
Engagement fields	Reactions/comments/shares available within approved scope	reactionCount, commentCount, shareCount, totalEngagement returned directly
Setup time	App review can take days	Minutes — add targets and run

Use the Graph API when you manage the Pages yourself and want an officially supported, write-capable integration. Use Facebook Photos Scraper With Engagement Analytics when you need engagement data on public pages and profiles you don't manage, without an app review process.

How to use Facebook Photos Scraper With Engagement Analytics

Facebook Photos Scraper With Engagement Analytics runs on the Apify platform — start it from its Store listing in Apify Console, or trigger it via the Apify API using your Apify account.

1. Open Facebook Photos Scraper With Engagement Analytics on the Apify Store and click Run, or call it via the API.
2. Add one or more public pages/profiles in pageTargets (e.g. "nike", "https://www.facebook.com/natgeo") — this is the input the Actor actually needs to do anything.
3. Set photoSampleSize and, optionally, minReactions to filter out low-engagement photos.
4. Enable proxyConfiguration (residential) for better coverage, then start the run.
5. Export results as JSON or CSV from the dataset, or read them via the API.

How to scale to bulk Facebook photo extraction

pageTargets accepts an array, so you add every page, profile, or handle you want measured — one per line — in a single run; there's no need to launch a separate run per target. Combine that with a higher photoSampleSize to pull a deeper sample per target in the same pass.

What can you do with Facebook photo data?

• A social media manager benchmarking creative uses reactionCount and totalEngagement to rank which photo styles get the strongest response before allocating ad spend.
• A brand monitoring analyst uses ownerName and accessibilityCaption to track how a competitor's page visual content is landing without opening each post manually.
• A content researcher archiving campaign visuals uses image and caption to build a searchable library of a brand's published photo content.
• A growth marketer combines minReactions filtering with commentCount to shortlist only the top-performing photos worth repurposing into new ads.
• An AI engineer feeds caption, accessibilityCaption, and the reactionCount/totalEngagement metrics into a RAG pipeline or agent tool to answer questions like "which of this brand's photos performed best" without manual review.

How does Facebook Photos Scraper With Engagement Analytics handle rate limits and blocking?

The Actor warms up a guest datr cookie before scraping so requests look like a real logged-out visitor, and rotates human-like browser headers and user agents per request. If a request comes back 403, 429, or 503, it escalates through a proxy fallback ladder — no proxy → Apify datacenter proxy → Apify residential proxy — and retries with randomized backoff. Each individual photo request retries up to 3 times before being skipped. Concurrency is capped (up to 20 photos in flight, with a connection limit of 10 total / 5 per host) to avoid hammering a single target. If a photo ultimately fails to parse or fetch, it is skipped and logged — the run continues with the remaining photos and targets rather than failing the whole job. No uptime or speed figure is published for this behavior; it reflects what the retry and proxy logic actually does.

⬇️ Input

Parameter	Required	Type	Description	Example value
pageTargets	No	array	Public Facebook pages or profiles to analyze — full URLs or short handles, one per line.	["nike", "https://www.facebook.com/natgeo"]
photoSampleSize	No	integer	Photos to analyze per target (1–10,000). Default 10.	25
includeEngagement	No	boolean	When true, includes reactionCount, commentCount, shareCount and totalEngagement. Default true.	true
minReactions	No	integer	Keep only photos with at least this many confirmed reactions. 0 keeps all. Default 0.	100
proxyConfiguration	No	object	Apify Proxy configuration; residential recommended for reliable coverage.	{ "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }

Example input

{
  "pageTargets": ["nike", "https://www.facebook.com/natgeo"],
  "photoSampleSize": 25,
  "includeEngagement": true,
  "minReactions": 100,
  "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}

⬆️ Output

Every run writes typed, normalized JSON rows to an Apify dataset — one row per photo, with the same field names on every run. Export as JSON, CSV, Excel, or any other format the Apify platform's dataset export supports.

Example output

{
  "id": "1122334455667788",
  "photoId": "1122334455667788",
  "facebookId": "1122334455667788",
  "dataType": "photo",
  "image": "https://scontent.xx.fbcdn.net/v/t39.30808-6/123456789_photo.jpg",
  "url": "https://www.facebook.com/photo.php?fbid=1122334455667788",
  "facebookUrl": "https://www.facebook.com/nike",
  "accessibilityCaption": "May be an image of one or more people and text",
  "caption": "Just do it. New drop out now.",
  "ownerId": "15087023444",
  "ownerName": "Nike",
  "reactionCount": 5120,
  "commentCount": 87,
  "shareCount": 42,
  "totalEngagement": 5249,
  "pageAdLibrary": { "id": "15087023444" },
  "inputUrl": "https://www.facebook.com/nike",
  "scrapedAt": "2026-07-25T09:00:00Z"
}

The default dataset view surfaces 15 of these 18 columns (it omits id, ownerId, and facebookId, which duplicate or extend photoId/ownerName) — export the full dataset as JSON to get every field. Fields shown as null mean Facebook did not expose that value logged out, never a fabricated 0.

How does it work?

Facebook Photos Scraper With Engagement Analytics starts at a page or profile's public /photos view, extracts embedded photo IDs directly from the page HTML, and, when pagination is available, keeps collecting more IDs through Facebook's own GraphQL pagination query. For each photo ID, it requests the same logged-out photo-viewer response a browser would get, parses the embedded feedback node for reaction, comment, and share totals, and computes totalEngagement locally. Requests go through a proxy fallback ladder (none → datacenter → residential Apify Proxy) with human-like headers and a warmed-up guest session cookie, retrying automatically on blocked responses. Only data visible to a logged-out visitor is ever returned — no login, no bypassing privacy settings. Because parsing targets Facebook's underlying data payload rather than its visual layout, the output schema stays stable even when Facebook's UI changes.

Integrations

Facebook Photos Scraper With Engagement Analytics works with the tools you already use to run and consume Apify Actors — direct API calls, AI agent frameworks, and no-code automation platforms.

Calling Facebook Photos Scraper With Engagement Analytics programmatically

from apify_client import ApifyClient

client = ApifyClient("<APIFY_API_TOKEN>")

run = client.actor("<YOUR_ACTOR_ID>").call(
    run_input={
        "pageTargets": ["nike"],
        "photoSampleSize": 25,
        "minReactions": 50,
    }
)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["reactionCount"], item["totalEngagement"])

Works in Go, Ruby, Node.js, cURL — any language that can make an HTTP request.

MCP integration for AI agents

Facebook Photos Scraper With Engagement Analytics is callable through Apify's MCP Server, which exposes Apify Actors as tools for MCP-compatible clients. Add this Actor's ID to the actors list when configuring Apify's MCP Server, then call it from Claude, or any other MCP client, the same way you'd call a local tool — no separate integration code required.

No-code tools (n8n, Make, LangChain)

In n8n, use the Apify node (or an HTTP Request node against the Actor's run endpoint) to trigger a run and pull dataset items into your workflow. In Make, use Apify's native app module to start a run and fetch the resulting dataset. In LangChain, use the Apify integration to call this Actor by ID and load its dataset items directly as Documents for a chain or agent.

Is it legal to scrape Facebook photos?

Scraping publicly available Facebook photos — content visible to any logged-out visitor — is generally permitted, though Facebook's Terms of Service restrict automated access and you remain responsible for how you use the data. Facebook Photos Scraper With Engagement Analytics returns only what a logged-out visitor can already see; it does not log in, bypass privacy settings, or collect anything hidden behind a login wall. Fields like ownerName, caption, and accessibilityCaption can constitute personal data under GDPR and CCPA, particularly when a photo's owner is an identifiable individual rather than a brand page — so any storage, profiling, or reuse of this data should rest on a documented lawful basis and honor deletion/access requests. Consult legal counsel if your use case involves bulk storage of personal data.

Frequently asked questions

What Facebook photo fields does Facebook Photos Scraper With Engagement Analytics return?

The core fields are reactionCount, commentCount, shareCount, totalEngagement, and caption/accessibilityCaption for text. See the data fields section above for the full 18-field row.

Does Facebook Photos Scraper With Engagement Analytics require a Facebook account or login?

No. It reads the same logged-out photo viewer Facebook serves any visitor and warms up its own guest session — you never supply Facebook credentials or cookies.

How many photos can I extract in one run?

photoSampleSize accepts 1–10,000 photos per target, and pageTargets accepts multiple pages/profiles in the same run, so total volume scales with how many targets you list.

What happens if a page or profile has no public photos, or the target can't be resolved?

The Actor returns 0 rows for that target, logs it as a failed target, and continues on to the remaining targets in the run rather than stopping the whole job or fabricating placeholder rows.

Can I scrape multiple Facebook pages or profiles at once?

Yes. pageTargets is an array — list every page, profile, or handle you want measured and they're all processed within a single run.

How does the engagement analytics actually work?

totalEngagement is a simple arithmetic sum of whichever of reactionCount, commentCount, and shareCount Facebook exposed for that photo — it is not a machine-learning score or sentiment analysis, and it deliberately excludes the per-reaction-type breakdown (like/love/wow/etc.), which Facebook does not expose to logged-out photo requests.

How is this different from Facebook Page Posts Scraper With Engagement Analytics?

This Actor is photo-scoped and reports aggregate reactionCount/commentCount/shareCount/totalEngagement only. Facebook Page Posts Scraper With Engagement Analytics operates on full page posts and additionally computes a per-type reaction breakdown, virality score, and engagement rank — use that Actor when you need post-level analytics rather than a photo gallery.

Does Facebook Photos Scraper With Engagement Analytics work with Claude, ChatGPT, and other AI agent tools?

Yes. It's reachable through Apify's MCP Server for MCP-compatible clients like Claude, and it's callable as a standard HTTP API endpoint from any other agent framework.

Does Facebook Photos Scraper With Engagement Analytics return data in a format LLMs can use directly?

Yes. Output is typed, normalized JSON with consistent field names across runs — no HTML parsing or selectors required. Pass it directly to an LLM, index it into a vector store, or feed it to an agent tool.

What happens when Facebook changes its layout or anti-bot system?

The Actor is maintained and its output schema is designed to stay stable across Facebook UI changes, since parsing targets the underlying data payload rather than page layout. No specific update turnaround time is published.

Can I use Facebook Photos Scraper With Engagement Analytics without managing proxies or browser infrastructure?

Yes. The Actor handles guest session warm-up, header rotation, and a proxy fallback ladder (none → datacenter → residential) internally — you only need to supply Apify Proxy access if you want the residential tier enabled.

Related scrapers

Scraper	What it extracts
Facebook Comments Scraper: Reaction Breakdown	Per-comment text plus the exact per-type reaction split
Facebook Page Posts Scraper With Engagement Analytics	Page posts with reaction breakdown and virality score
Facebook Groups Posts & Media Scraper	Posts and media from public Facebook Groups
Facebook Reels Scraper	Public Facebook Reels video metadata and engagement
Facebook Ads Library Scraper & Creative Media	Ad creatives and metadata from Meta's Ads Library

Your feedback

Found a bug or missing a field? Open an issue on this Actor's Issues tab on the Apify Store, or reach out through Scraper-Engine's Apify Store profile. Reports like these directly shape what gets fixed and added next.