FB Profile Scraper
Pricing
from $0.01 / result
Pricing
from $0.01 / result
Rating
0.0
(0)
Developer
Dev with Bobby
Maintained by CommunityActor stats
15
Bookmarked
974
Total users
67
Monthly active users
4.1 hours
Issues response
12 days ago
Last modified
Categories
Share
Facebook Profile & Page Scraper
Extract comprehensive Facebook profile and page data with a single click. Enter usernames or URLs and get structured data including followers, likes, contact information, and engagement metrics.
Features
- Flexible Input - Accepts usernames, full URLs, or mixed formats
- Complete Profile Data - Name, bio, followers, likes, categories, verification status
- Contact Information - Email, phone, website, address when available
- Visual Assets - Profile pictures and cover photos
- Engagement Metrics - Calculated engagement rates and audience size categories
- Anti-Detection - Session management, proxy rotation, rate limiting
- Controlled Reliability - Bounded fallback stages finish before the Actor timeout and report every non-usable outcome separately
Quick Start
Step 1: Enter Profiles
Paste Facebook usernames or URLs (one per line):
nasaearthChrisBrecheensWritingAboutWritinghttps://www.facebook.com/UNclimatechangefacebook.com/some-company
Step 2: Run the Actor
Click Start and wait for extraction to complete.
Step 3: Download Results
Get your data as JSON, CSV, or Excel from the Storage tab.
Input Options
| Parameter | Type | Default | Description |
|---|---|---|---|
profiles | String | (required) | Facebook usernames or URLs, one per line |
mode | String | fast | Extraction strategy: Fast (recommended), Balanced, or Deep |
proxyType | String | BUYPROXIES94952 | Proxy type: Datacenter, Residential, or Static US |
maxConcurrency | Integer | 2 | Parallel pages (1-5) |
maxRequestsPerMinute | Integer | 15 | Rate limit (5-30) |
maxProfiles | Integer | 10 | Max profiles per run (cost control) |
maxRuntimePerProfileSecs | Integer | 25 | Browser fallback runtime budget per profile |
requireAuthenticatedData | Boolean | false | Skip HTTP-first optimization for richer authenticated extraction |
cookies | String | (optional) | Facebook session cookies for authenticated scraping |
Supported Input Formats
All of these formats work:
Avoid non-profile Facebook paths (for example: `/events`, `/reel`, `/watch`, `/groups`).These URLs are now skipped automatically to prevent wasted runtime and proxy spend.## Extraction Modes- **Fast (Recommended):** HTTP-first extraction with limited browser fallback. Best profitability.- **Balanced:** HTTP-first plus more browser anti-block handling and popup dismissal.- **Deep:** Browser-focused extraction for maximum completeness at higher cost.The Actor now defaults to Fast mode to keep runtime and proxy usage low.nasaearthNASA Earthhttps://www.facebook.com/nasaearthfacebook.com/nasaearthwww.facebook.com/nasaearth/
Output
Sample Output
{"inputUrl": "https://www.facebook.com/nasaearth","scrapedUrl": "https://www.facebook.com/nasaearth","profileType": "page","name": "NASA Earth","username": "nasaearth","facebookId": "123456789","verified": true,"followers": 10921894,"likes": 10505363,"about": "Explore and learn more about our home planet.","categories": ["Science Website"],"profilePicture": "https://scontent.xx.fbcdn.net/...","coverPhoto": "https://scontent.xx.fbcdn.net/...","email": "contact@nasa.gov","website": "science.nasa.gov/earth","engagementRatio": "0.962","audienceSize": "Large (1M+)","isComplete": true,"scrapedAt": "2026-01-26T12:30:45.123Z"}
Output Fields
| Field | Type | Description |
|---|---|---|
inputUrl | String | Original URL/username provided |
scrapedUrl | String | Final URL after redirects |
profileType | String | page, profile, or unknown |
name | String | Display name |
username | String | Facebook username/handle |
facebookId | String | Numeric Facebook ID |
verified | Boolean | Official verification status |
followers | Integer | Number of followers |
likes | Integer | Number of page likes |
about | String | Bio/description |
categories | Array | Page categories |
profilePicture | String | Profile image URL |
coverPhoto | String | Cover image URL |
email | String | Contact email (if available) |
phone | String | Contact phone (if available) |
website | String | Website URL (if available) |
address | String | Physical address (if available) |
engagementRatio | String | Likes-to-followers ratio |
audienceSize | String | Size category (Micro/Small/Medium/Large) |
extractionStage | String | http or browser stage used to produce the result |
extractionModeUsed | String | Mode used for extraction (fast, balanced, deep) |
durationMs | Integer | Approximate extraction time for this profile |
isComplete | Boolean | Whether all data was extracted |
wasBlocked | Boolean | Whether extraction was blocked |
resultStatus | String | success for usable, billable dataset records |
isUsable | Boolean | Name and canonical URL plus at least one useful profile signal were extracted |
attemptCount | Integer | Total HTTP and browser attempts made for the profile |
fallbackStages | Array | Extraction stages attempted (primary_http, residential_http, browser) |
Reliability and Success Metrics
The Actor reports two different kinds of success:
- Actor run success means the pipeline finished cleanly and produced a controlled terminal outcome for every unique input. A blocked or unavailable Facebook profile does not crash the whole run.
- Item success is reported as
itemSuccessRatein theSUMMARYkey-value record. A usable item must contain a real profile name, a canonical Facebook URL, and at least one useful signal such as an ID, followers/likes, bio, image, category, or contact field.
Only usable results are written to the default dataset and charged as results. Invalid, blocked, unavailable, timed-out, and internal-error outcomes are written to the FAILURES key-value record. The output page links to both SUMMARY and FAILURES.
The run uses a 540-second soft deadline under the 600-second platform timeout. When the remaining budget is too small for another expensive fallback, the Actor stops starting work, records RUNTIME_BUDGET_EXCEEDED, writes diagnostics, and exits cleanly.
Authentication (Optional)
For higher success rates, provide your Facebook session cookies. Valid cookies take effect in all modes (including Fast). Authenticated runs start directly in one sticky browser/proxy session, which avoids replaying the same Facebook session across changing datacenter and residential IPs.
- Log into Facebook in your browser
- Install the Cookie-Editor browser extension
- Click the extension icon on facebook.com
- Click Export > Export as JSON
- Paste the JSON array in the
cookiesfield
Cookies expire. Facebook rotates the
xssession cookie frequently. Make sure your export includes bothc_userandxs; if a run is still blocked while authenticated, the log will warn that your cookies are likely expired — re-export fresh ones from a logged-in session.
Cookie Format
[{"name": "c_user", "value": "YOUR_USER_ID", "domain": ".facebook.com"},{"name": "xs", "value": "YOUR_SESSION", "domain": ".facebook.com"}]
Proxy Options
| Option | Description | Best For |
|---|---|---|
BUYPROXIES94952 | Datacenter proxies (default) | Cost-effective general scraping |
RESIDENTIAL | Residential proxies | Higher success rate, premium cost |
StaticUS3 | Static US IPs | Consistent identity across requests |
Residential fallback (on by default): Facebook heavily blocks datacenter IPs. The Actor first tries primary HTTP extraction, then makes at most one residential HTTP rescue stage and one browser stage for profiles that still lack usable data. Each transient HTTP stage can retry once. Authenticated runs start directly in a sticky browser session so Facebook cookies are not replayed while rotating between datacenter and residential IPs. Set enableResidentialFallback to false to keep browser fallback on the primary proxy.
Use Cases
Marketing & Social Media
- Competitor analysis and benchmarking
- Influencer research and discovery
- Campaign planning and audience research
- Brand monitoring
Business Intelligence
- Lead generation and prospecting
- Market research
- Partnership research
- Content strategy analysis
Research & Analysis
- Academic social media research
- Market trend analysis
- Communication studies
Technical Details
Anti-Detection Measures
- Session Pool - Uses one browser/proxy identity per profile; authenticated cookies are not rotated across HTTP proxy stages
- Proxy Rotation - Distributes requests across IPs
- Rate Limiting - Configurable request throttling
- Random Delays - Human-like timing between requests
- Login Popup Dismissal - Handles Facebook modals automatically
Limitations
- Public data only - Cannot access private profiles
- Rate limits - Facebook may block after many requests
- Login walls - Some pages trigger login requirements
- Dynamic content - Some data may not be available on all pages
Best Practices
- Start with Fast mode for best margin and scale
- Keep concurrency low (1-2) to avoid blocks
- Use residential proxies only for difficult pages
- Provide cookies for authenticated access when needed
- Space out runs to avoid IP blocks
Cost Estimation
- Datacenter proxy: ~$0.25 per 1000 requests
- Residential proxy: ~$12.50 per 1000 requests
- Compute: ~$0.10 per 100 profiles
Error Handling
The scraper handles common issues gracefully:
- Blocked profiles - Recorded in
FAILURESwith a stable failure code - Private/unavailable profiles - Terminate without wasteful proxy retries
- Invalid URLs - Recorded without starting network work
- Transient HTTP/browser failures - Retried at most once within the global time and cost budget
- Run deadline - Stops new rescue work early enough to persist
SUMMARYandFAILURES
Support
For issues or feature requests, contact the author or open an issue on the Actor's page.