Facebook Profile Scraper
Pricing
from $2.00 / 1,000 scraped results
Facebook Profile Scraper
Extract names, profile URLs, descriptions, follower counts, profile images, and Open Graph metadata from usernames or profile links. Supports Apify Proxy, batch processing, and structured dataset export.
Pricing
from $2.00 / 1,000 scraped results
Rating
0.0
(0)
Developer
Data Pilot
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
π Facebook Profile Scraper is a powerful Apify Actor designed to discover, track, and collect public Facebook Profile data directly from Facebook's own profile pages using a full browser engine. This tool provides comprehensive Facebook Profile intelligence including display name, description, follower/likes count, profile picture, and canonical profile URL for any accessible Facebook Profile. Whether you're building a brand-monitoring dashboard, tracking public pages, or conducting social media research, the Facebook Profile Scraper delivers actionable Facebook Profile insights efficiently.
With direct browser automation, OpenGraph metadata extraction, username/URL normalization, and reliable Apify Dataset delivery, the Facebook Profile Scraper ensures comprehensive Facebook Profile coverage across any list of usernames or profile links. It focuses on key Facebook Profile signals including name, description, followers, and profile picture, making it an essential tool for social media research and brand intelligence.
π Table of Contents
- Features
- Data Source
- How It Works
- Input
- Output
- Technical Stack
- Data Fields
- Use Cases
- Quick Start
- Configuration
- Performance
- Billing
- Important Notes
- Changelog
- Support
- License & Legal
π₯ Features
- Real Browser Rendering β with headless Chromium to load each Facebook Profile exactly as a real visitor would.
- Flexible Input Handling β Accepts plain usernames,
@handles, or full Facebook Profile URLs and normalizes them automatically. - OpenGraph Metadata Extraction β Pulls name, description, image, and canonical URL straight from each Facebook Profile's meta tags.
- Follower/Likes Detection β Parses follower or "people follow this" counts directly out of the Facebook Profile description text.
- 404 Detection β Automatically detects and skips Facebook Profile pages that no longer exist.
- Residential Proxy Support β Apify residential proxy routed through for reliable Facebook Profile access.
- Realistic Browser Fingerprint β Custom user agent and viewport to reduce detection while loading each Facebook Profile.
- Batch Processing β Scrape any number of Facebook Profile entries in a single run.
- Human-Like Pacing β Built-in delay between Facebook Profile page loads to reduce blocking.
- Real-Time Dataset Push β Pushes all collected Facebook Profile records to Apify Dataset in a single batch.
- Detailed Logging β Comprehensive per-username Facebook Profile navigation and status logging.
- Graceful Error Handling β Skips a failing Facebook Profile without stopping the whole run.
π Data Source
Facebook Public Profile Pages
- Authority: Facebook's own public-facing profile and page pages
- Access Method: Headless Chromium browser via , rendering
facebook.com/{username} - Coverage: Any public Facebook Profile or Page reachable without login
- Data: OpenGraph metadata β name, description, image, URL, and follower/likes count
- Access: Public pages, no API key required
- Update Frequency: Reflects each Facebook Profile's current live state at time of run
βοΈ How It Works
The Facebook Profile Scraper accepts a list of usernames or profile URLs, normalizes each into a clean username, and drives a real headless Chromium browser to each Facebook Profile page. Once the page loads, the Actor parses the rendered HTML with BeautifulSoup to extract OpenGraph meta tags β title, description, image, and canonical URL β and applies a regular expression to pull a follower or likes count out of the description text where available. Every successfully scraped Facebook Profile record is collected and pushed to the Apify Dataset in a single batch at the end of the run.
Key Processing Steps:
- Input Parsing β Accept a list of usernames, handles, or full Facebook Profile URLs
- Username Normalization β Strip
@symbols and extract the username from full URLs - Proxy Setup β Configure Apify residential proxy and pass credentials into
- Browser Launch β Start headless Chromium with a realistic user agent and viewport
- Profile Loop β Iterate through each normalized Facebook Profile username
- Page Navigation β Load
facebook.com/{username}and wait for DOM content - 404 Check β Detect and skip missing Facebook Profile pages
- HTML Parsing β Extract OpenGraph meta tags with BeautifulSoup
- Follower Extraction β Regex-match a follower/likes count from the description
- Timestamp Tagging β Record scrape time per entry
- Rate Limiting β Apply a short delay between Facebook Profile loads
- Dataset Push β Push all collected records from the run in a single batch
Key Benefits:
- Pull Facebook Profile data for any public account or page without manual visits
- Detect missing or deactivated Facebook Profile pages automatically
- Monitor brand pages and public figures' Facebook Profile metadata over time
- Feed social media dashboards, research pipelines, or brand-monitoring tools
- Automate recurring Facebook Profile checks as descriptions or follower counts change
π₯ Input
The Actor accepts the following input parameters:
| Field | Type | Default | Description |
|---|---|---|---|
profiles | array | (required) | List of Facebook Profile usernames, @handles, or full profile URLs. |
useApifyProxy | boolean | true | Enable Apify residential proxies. |
apifyProxyGroups | array | ["RESIDENTIAL"] | Proxy group configuration. |
Example Input:
{"profiles": ["zuck","@nasa","https://www.facebook.com/natgeo"],"useApifyProxy": true,"apifyProxyGroups": ["RESIDENTIAL"]}
Scrape a Single Facebook Profile:
{"profiles": ["natgeo"]}
Scrape from Full Profile URLs:
{"profiles": ["https://www.facebook.com/nasa","https://www.facebook.com/natgeo"]}
π€ Output
The Actor pushes Facebook Profile records with the following structure:
| Field | Type | Description |
|---|---|---|
username | string | The normalized Facebook Profile username used for the request |
full_name | string | Display name extracted from the OpenGraph title tag |
profile_url | string | Canonical Facebook Profile URL from OpenGraph metadata |
description | string | OpenGraph description text for the Facebook Profile |
followers_count | string/null | Follower or likes count parsed from the description, if present |
profile_pic | string | URL of the Facebook Profile picture from OpenGraph image metadata |
scraped_at | string | ISO 8601 timestamp of when the record was scraped |
Example Facebook Profile Record:
{"username": "natgeo","full_name": "National Geographic","profile_url": "https://www.facebook.com/natgeo/","description": "National Geographic. 45M likes. Experience the world through the eyes of National Geographic photographers.","followers_count": "45M","profile_pic": "https://scontent.xx.fbcdn.net/...","scraped_at": "2026-08-05T09:00:00+00:00"}
π§° Technical Stack
- **Browser Automation:**with headless Chromium for real Facebook Profile rendering
- HTML Parsing: BeautifulSoup for OpenGraph metadata extraction
- Pattern Matching: Regular expressions for follower/likes count parsing
- Date Handling:
datetimewith timezone-aware UTC timestamps - Async:
asynciofor non-blocking, multi-profile processing - Proxy: Apify Proxy with
RESIDENTIALconfiguration, wired into 's proxy settings - Logging: Apify Actor logging system
- Platform: Apify Actor serverless environment
π Data Fields Explained
Identity
- username: The normalized handle used to build the Facebook Profile URL
- full_name: The public display name shown on the Facebook Profile
Profile Details
- description: The OpenGraph description summarizing the Facebook Profile
- profile_url: The canonical link to the Facebook Profile
- profile_pic: Direct link to the Facebook Profile picture
Engagement
- followers_count: Follower or "likes"/"people follow this" figure extracted from the description, when Facebook exposes it publicly
π― Use Cases
- Brand Monitoring β Track how a company's Facebook Profile or Page presents itself publicly
- Competitor Research β Compare follower counts and descriptions across competing Facebook Profile pages
- Public Figure Tracking β Monitor Facebook Profile metadata for politicians, creators, or organizations
- Social Media Auditing β Verify that a Facebook Profile is active and correctly configured
- Marketing Analytics β Feed Facebook Profile metadata into campaign or reputation dashboards
- Lead Generation β Identify public business pages matching a target market
- Academic Research β Study public Facebook Profile trends at scale
- OSINT Research β Gather publicly available Facebook Profile metadata for investigations
π Quick Start
1. Prepare Input
Go to Apify Console and enter:
{"profiles": ["nasa", "natgeo"]}
2. Run the Actor
Click Start. The Actor will:
- Normalize each username or URL into a clean Facebook Profile handle
- Launch a headless browser and visit each Facebook Profile page
- Extract OpenGraph metadata and follower counts
- Push all results to the Dataset
3. Monitor Progress
Console shows:
Initializing Facebook Scraper for 2 account(s)...[Facebook Scraper] Navigating to: 'https://www.facebook.com/nasa'[Facebook Scraper] Navigating to: 'https://www.facebook.com/natgeo'Done! Successfully saved 2 Facebook profile(s) to Dataset.
4. View & Download Results
- Results Tab: All Facebook Profile records
- Export: JSON, CSV, Excel, or HTML
- Filter: By follower count or username
- API Access: Available via the Apify API
βοΈ Configuration
Single Facebook Profile:
{"profiles": ["natgeo"]}
Mixed usernames and URLs:
{"profiles": ["@nasa","https://www.facebook.com/natgeo"]}
Run without proxy:
{"profiles": ["natgeo"],"useApifyProxy": True}
π Performance
Processing Speed
- One full browser page load per Facebook Profile
- Fixed ~3 second settle time per page load plus a 2 second delay between profiles
- Scales linearly with the number of usernames/URLs submitted
Resource Usage
- Memory: Moderate, due to running a real Chromium browser instance
- Network: One page navigation per Facebook Profile, plus associated page assets
- Proxy: One residential proxy session shared across the browser context for the run
π° Billing
Batch Billing
- Billing Model: Batch push (not per-record PPE)
- Typical Cost: Proportional to total Facebook Profile pages successfully scraped
- Efficiency: Single shared browser session across all profiles in a run keeps overhead low
β οΈ Important Notes
Legal & Compliance
- Fair Use: Respects Facebook's public pages and applies pacing delays between requests
- Public Data Only: Retrieves only publicly visible Facebook Profile metadata exposed via OpenGraph tags
- Privacy: Collecting profile data may be subject to privacy regulations and Facebook's Terms of Service β use only for legitimate purposes
- Legal: Not legal advice β consult qualified professionals before using this data for compliance-sensitive decisions
Data Quality
- Freshness: Reflects each Facebook Profile's live state at time of run
- Completeness: Follower/likes counts are only available when Facebook exposes them in the public description text
- Accuracy: Sourced directly from Facebook's own rendered pages
- Verification: Cross-check high-stakes figures against the live Facebook app or website
Best Practices
- Always configure a residential proxy for the most reliable Facebook Profile access
- Use full profile URLs when a username alone is ambiguous
- Keep batch sizes reasonable, since each Facebook Profile requires a full browser page load
- Re-run periodically to track changes in description or follower counts
- Expect
followers_countto benullfor Facebook Profile pages that don't expose it publicly
π¦ Changelog
v1.0.0 (August 2026)
Initial Release:
- headless Chromium browser automation
- Username/URL normalization for flexible input
- OpenGraph metadata extraction via BeautifulSoup
- Follower/likes count regex parsing
- 404 detection for missing profiles
- Apify residential proxy support wired into
- Real-time Dataset push
- Asyncio-based batch processing
π§βπ» Support & Feedback
- Issues: Submit via Apify console with the username or URL used
- Documentation: Check the Actor details page
- Community: Apify forum discussions
- Feature Requests: Suggest additional Facebook Profile fields to extract
- Bug Reports: Include the username/URL, expected result, and error details
π License & Legal
Terms of Use:
- Use for legitimate research, marketing, and analytics purposes
- Respect Facebook's Terms of Service
- Do not use for unsolicited contact, harassment, or unlawful surveillance
- Use Facebook Profile data responsibly and in compliance with applicable privacy laws
Disclaimer: Facebook Profile Scraper is provided as-is for research and analytics purposes. Users are responsible for compliance with Facebook's ToS and all applicable laws. This is not legal advice.
π Get Started Today
Deploy now for Facebook Profile research!
Use for:
- π Brand & Page Monitoring
- π Competitor Account Tracking
- π‘ Social Media Analytics
- π Public Figure Tracking
- π― OSINT & Reputation Research
Perfect for:
- Social Media Marketers
- Brand Monitoring Teams
- Growth & Analytics Teams
- OSINT Researchers
Last Updated: August 2026 Version: 1.0.0 Status: Production Ready Platform: Apify Actor Architecture: Async/Await Data Source: Facebook Public Profile Pages
π Related Tools
- Instagram Profile Scraper
- Twitter/X Profile Collector
- TikTok Profile Scraper
βοΈ Facebook Profile Excellence
This Actor is optimized for Facebook Profile research with:
- β Real browser rendering for accurate data
- β Flexible username/URL input handling
- β OpenGraph metadata extraction
- β 404 and missing-profile detection
- β Real-time Dataset push
- β Production-ready code