Extract Portfolio Data with Behance Dribbble Scraper

To extract structured portfolio metadata and creative project details from Behance and Dribbble, deploy the Behance Dribbble Scraper. This single actor operates across five execution modes (designerProfile, projectByUrl, projectSearch, trendingProjects, and byCategory) to extract profile statistics, work experience history, engagement counts, social links, and availability flags without requiring user logins or browser session pre-warming.

Scraper architecture and execution modes

Designing automated data collection pipelines across portfolio platforms requires understanding how target sites render content. Behance, owned by Adobe, embeds server-side JSON structures within public profile pages. Specifically, Behance embeds a server-side JSON blob (beconfig-store_state) containing deep structured profile metadata. This enables extraction of stats, work experience history, city and country attributes, social links, and availability flags.

In contrast, Dribbble profile pages rely heavily on client-side JavaScript rendering. When fetching Dribbble profiles without executing JavaScript, extraction yields lightweight open graph meta tags, specifically display name, bio, and avatar image URLs.

The Behance Dribbble Scraper addresses anti-bot challenges on both platforms by using curl_cffi Chrome-131 TLS impersonation. Both Adobe Edge CDN (which fronts Behance) and Cloudflare (which fronts Dribbble) inspect TLS fingerprints. By impersonating Chrome-131 TLS signatures, requests pass through Web Application Firewalls (WAFs) over raw connections without needing proxy pre-warming or session warmup.

When unexpected blocking occurs, the actor relies on built-in proxy auto-escalation. If autoEscalateOnBlock is set to true (its default setting), encountering an HTTP 403 or anti-bot challenge on a raw datacenter IP triggers an automatic switch to Apify Proxy, attempting datacenter proxies first and falling back to residential proxies if needed.

Data schemas emitted by the actor adhere to clean structural rules. Empty fields are dropped from every record at every depth, keeping output objects concise and removing null noise from downstream ingestion databases.

Practical use cases

Use case 1: Recruiting and talent pipeline sourcing

Outcome: Build an actionable database of available design candidates filtered by creative discipline, minimum audience threshold, and availability status.

Question to answer: Which qualified designers on Behance match our follower threshold and are currently flagged as available for freelance or full-time hire?

Configure: Set platform to behance and mode to designerProfile. Provide candidate handles or profile URLs in usernames. Enable availableForHireOnly by setting it to true, set minFollowers to 1000, and set maxItems to 100.

Working method: Run the actor to fetch designer profiles directly from Behance profile URLs. The actor parses server-side JSON configuration structures (beconfig-store_state) to extract work experience history, location attributes, follower statistics, and direct availability flags.

Deliverable: A dataset of designer records containing recordType set to designer, displayName, occupation, city, country, workExperience arrays, socialLinks, and availableForHire set to true.

Stop condition: Stop execution when all submitted designer handles have been processed or when the maxItems limit is reached.

Use case 2: Creative tool adoption and project trend analysis

Outcome: Monitor published projects, creative tool usage, and engagement metrics across specific design disciplines over time.

Question to answer: Which specific creative tools and topical fields correlate with higher view counts and appreciations across trending projects on Behance?

Configure: Set mode to projectSearch or byCategory. Select platform as behance. Set behanceField to ui-ux or branding, and select behanceTool such as figma or photoshop. Set behanceSort to appreciations or views, and define maxItems to 200.

Working method: Initiate catalog runs across target creative categories or search queries. The actor collects project records directly, capturing project titles, descriptions, cover image URLs, appreciationsCount, viewsCount, commentsCount, tags, tools, and owner user objects.

Deliverable: Structured project records containing recordType set to project, name, description, coverImageUrl, engagement metrics, tags, tools list, and owners array.

Stop condition: Stop collection when the requested number of project records matching maxItems has been retrieved for the target creative category.

Use case 3: Dribbble shot and creator profile benchmarking

Outcome: Rapidly track new popular shots and top visual creators on Dribbble for design inspiration and outbound engagement.

Question to answer: What are the top trending visual shots published on Dribbble within a given timeframe, and who created them?

Configure: Set platform to dribbble and mode to trendingProjects or byCategory. Set dribbbleTimeframe to week or month, or set dribbbleTag to mobile or web-design. Set maxItems to 50.

Working method: Run the actor against Dribbble catalog endpoints. The scraper processes shot pages and extracts open graph meta tags to retrieve lightweight creator details alongside shot identifiers and media links.

Deliverable: Structured shot records containing recordType set to shot, id, name, url, description, coverImageUrl, and creator owner metadata.

Stop condition: Terminate execution once the specified maxItems threshold of trending shots for the selected timeframe or tag is filled.

Step-by-step operating workflow

1. Identify extraction scope and target platform: Determine whether your team requires deep profile metrics and work history (Behance) or lightweight meta tags and popular shots (Dribbble), then select the matching mode.
2. Run a small validation test: Execute a trial run of Behance Dribbble Scraper with maxItems set to 5 or 10 records to inspect the JSON output structure.
3. Apply targeted filtering parameters: Set platform parameters, input usernames or gallery URLs, and configure optional filters like minFollowers, availableForHireOnly, behanceField, or behanceTool.
4. Execute collection and monitor proxy auto-escalation: Launch the run. The actor utilizes curl_cffi Chrome-131 TLS impersonation over direct connection. If an HTTP 403 block occurs, autoEscalateOnBlock automatically engages Apify Proxy.
5. Ingest and handle schema variations: Inspect records to ensure required attributes are populated. Remember that empty fields are dropped from every record at every depth, requiring flexible dictionary parsing in downstream pipelines.
6. Export dataset records: Route structured dataset outputs to CRM systems, talent databases, or trend analysis pipelines.

Distinct actor roles

The Behance Dribbble Scraper acts as a unified collection engine for design platforms. In designerProfile mode, it operates as a profile metadata extractor. In projectByUrl, projectSearch, trendingProjects, and byCategory modes, it acts as a project and shot catalog parser.

Operational limits and data quality

Operating web scrapers against media-heavy platforms requires clear awareness of structural and technical boundaries:

• Asymmetrical platform depth: Behance profile pages contain server-side JSON structures (beconfig-store_state) providing detailed work experience, total appreciations, city, country, and availability flags. Dribbble profile pages rely on JavaScript rendering, so unrendered fetches yield open graph meta tags (display name, bio, and avatar).
• Missing field handling: Empty fields are dropped from every record at every depth. Pipelines must use defensive key lookup rather than expecting fixed schemas.
• Anti-bot and WAF navigation: Adobe Edge CDN (Behance) and Cloudflare (Dribbble) perform TLS fingerprinting. The actor uses curl_cffi Chrome-131 impersonation to pass WAF checks without proxy overhead until blocked.
• Automatic proxy escalation: When an HTTP 403 block occurs and autoEscalateOnBlock is true, the actor engages Apify Proxy (datacenter proxies first, then residential proxy fallback).
• Non-existent usernames: When a username is not found, the actor logs a warning and continues processing remaining items in the queue.
• Record cap boundaries: Output is bounded by the maxItems parameter (configurable between 1 and 1000 records).

Frequently asked questions

Do I need platform login accounts to run this scraper?

No. Both Behance and Dribbble expose public profiles and project pages anonymously without requiring user authentication.

Why does Behance return richer designer data than Dribbble?

Behance embeds a server-side JSON configuration store (beconfig-store_state) containing detailed stats, work history, social links, and availability flags. Dribbble profile pages rely on JavaScript rendering, returning display name, bio, and avatar when fetched without JavaScript execution.

How does the scraper handle anti-bot blocks?

The actor uses curl_cffi Chrome-131 impersonation to match real browser TLS fingerprints. If an anti-bot HTTP 403 block occurs, autoEscalateOnBlock automatically engages Apify Proxy to retry the request transparently.

What happens if a requested username does not exist?

The actor logs a warning and continues processing the next username in the batch.

Why are some JSON fields missing from certain records?

The actor drops empty fields from every record at every depth. If a designer has not listed an occupation, location, or work experience, those keys are omitted from the output record.

Resources

• Behance Dribbble Scraper Actor Page