Dribbble Scraper - Design Shots & Designer Data

Scrape Dribbble shots and designer data in bulk. Extract shot title, URL, full-size image, designer name, profile URL and designer ID from any tag or feed to CSV/JSON. No API key, no login.

---

What does the Dribbble Scraper do?

This Actor turns any Dribbble search into a structured dataset. You give it by tag or by feed URL, it walks the result pages one after another, and it writes one clean row per shot into your dataset — ready to export as JSON, CSV or Excel, or to pull straight from the Apify API.

Dribbble renders its shot grid server-side, tagging every card with the shot ID, title, designer and image set. The Actor reads those cards straight from the HTML, so it needs no browser and no account. Pagination is followed automatically until it runs out of results, hits your page limit or hits your Max items cap, whichever comes first. Every row is de-duplicated across the whole run, so you are never billed twice for the same shot.

There is no API key, no login and no browser involved. That keeps runs fast and cheap, and it means you can schedule the Actor without worrying about credentials expiring.

Who is it for?

• Design recruiters building shortlists of designers working in a given style.
• Creative agencies sourcing freelance talent by visual direction rather than keyword.
• Design leads tracking visual trends across a discipline over time.
• Lead-generation teams compiling designer profile lists for outreach.
• Researchers and educators assembling a labelled dataset of design work.

Use cases

• Export every shot for a tag such as branding and pull the designers behind the best work.
• Build a designer prospect list with profile URLs ready for enrichment.
• Track which visual styles trend on the popular feed week by week.
• Assemble a labelled image dataset of design work with titles.
• Monitor how a competitor's design team publishes work over time.

Why use this Dribbble Scraper?

• 🔑 Keyless — no account, no API token, no cookies to paste.
• 📦 11 fields per shot — everything the result page exposes, already typed.
• 📄 Real pagination — it walks page after page instead of returning the first screen.
• 🎯 Precise caps — Max items stops the run exactly where you want it, so the bill is predictable.
• 📊 Export anywhere — JSON, CSV, Excel or HTML, plus the Apify API and integrations.
• 💸 Pay per result — you pay for rows you actually receive, with no platform fees to calculate.

What data can you extract?

Every run produces one row per shot, with these fields:

Field	Type	Description
shotId	string	Dribbble shot ID
title	string	Shot title
shotUrl	string	Full shot URL
imageUrl	string	Largest available shot image URL
designerName	string	Designer or team display name
designerUrl	string	Designer or team profile URL
designerId	string	Dribbble user ID of the designer
tag	string	Tag or feed this row came from
page	number	Result page the shot appeared on
position	number	Rank of the shot within the run
scrapedAt	string	ISO timestamp of extraction

Output example

{
  "shotId": "27721266",
  "title": "Nexora - AI-Powered B2B E-Commerce Landing Page",
  "shotUrl": "https://dribbble.com/shots/27721266-Nexora-AI-Powered-B2B-E-Commerce-Landing-Page",
  "imageUrl": "https://cdn.dribbble.com/userupload/48985061/file/dd8871dc.png?format=webp&resize=1200x900",
  "designerName": "Korsa",
  "designerUrl": "https://dribbble.com/korsaagency",
  "designerId": "12666113",
  "tag": "branding",
  "page": 1,
  "position": 1,
  "scrapedAt": "2026-09-11T09:30:11.552Z"
}

How to use

Option A — by tag

{
  "tags": [
    "branding",
    "illustration"
  ],
  "sortBy": "recent",
  "maxPagesPerSearch": 15,
  "maxItems": 700
}

1. Open the Actor and fill in the tag field.
2. Set Max pages per search and Max items to bound the run.
3. Click Start, then export from the Output tab.

Option B — by feed URL

{
  "startUrls": [
    {
      "url": "https://dribbble.com/shots"
    }
  ],
  "sortBy": "popular",
  "maxPagesPerSearch": 20,
  "maxItems": 500
}

Paste one or more Dribbble URLs into Start URLs and the Actor paginates each of them independently.

Input parameters

Parameter	Type	Default	Description
tags	array	–	Dribbble tags to crawl, e.
sortBy	string	popular	Which Dribbble feed to read.
startUrls	array	[]	Dribbble listing URLs to crawl instead of, or in addition to, the tags above.
maxPagesPerSearch	integer	8	How many result pages to walk for each search.
maxItems	integer	500	Stop after this many shots.
maxConcurrency	integer	3	Parallel requests.
proxyConfiguration	object	{"useApifyProxy": true}	Proxy used to fetch pages.

Tips for best results

• Use a tag such as branding, mobile or illustration for focused results, or leave it empty for the main shots feed.
• Dribbble returns 24 shots per page, so plan page counts accordingly.
• De-duplicate on designerId when you want a list of people rather than a list of shots.
• recent surfaces new work and is the better feed for trend tracking; popular is better for quality.
• imageUrl points at the largest rendition Dribbble serves, ready to download.
• Schedule a weekly run on the same tag to watch a niche evolve.
• designerUrl is the profile page — enrich it separately if you need contact details.
• Keep Max concurrency low; Dribbble is sensitive to rapid parallel requests.
• The feed repeats itself once exhausted, and the Actor stops automatically when that happens.
• Pair with the website contact scraper to turn designer profiles into an outreach list.

Integrations

Send results straight into the tools you already use: Google Sheets, Slack, Zapier, Make, Airtable or any Webhook. You can also schedule the Actor to run hourly, daily or weekly and have each run append to the same dataset, which is how you build a price or availability history rather than a one-off snapshot.

API usage

Run the Actor and collect results from any language. Replace <YOUR_TOKEN> with your Apify API token.

cURL

curl -X POST "https://api.apify.com/v2/acts/logiover~dribbble-shots-scraper/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"tags": ["branding", "illustration"], "sortBy": "recent", "maxPagesPerSearch": 15, "maxItems": 700}'

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_TOKEN>' });
const run = await client.actor('logiover/dribbble-shots-scraper').call({"tags": ["branding", "illustration"], "sortBy": "recent", "maxPagesPerSearch": 15, "maxItems": 700});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient

client = ApifyClient('<YOUR_TOKEN>')
run = client.actor('logiover/dribbble-shots-scraper').call(run_input={"tags": ["branding", "illustration"], "sortBy": "recent", "maxPagesPerSearch": 15, "maxItems": 700})
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)

Use with AI agents (MCP)

This Actor is available through the Apify MCP server, so an AI agent can call it as a tool. Point your agent at https://mcp.apify.com and it can run the Dribbble Scraper on demand — for example: "Pull the first 500 shots from Dribbble and summarise the price distribution." The agent receives the same structured rows you would get from the UI.

FAQ

Do I need a Dribbble account or API key?

No. The Actor reads publicly available pages only. There is nothing to authenticate and no credentials to rotate.

How many shots can I get in one run?

As many as the search exposes. Raise Max pages per search and Max items together; the run stops at whichever limit it reaches first.

Why did I get fewer rows than I asked for?

The search ran out of shots. That is normal for narrow queries — broaden the search or add more searches to one run.

Are results de-duplicated?

Yes. Each shot is emitted once per run, even when it appears on several pages, so you are never billed twice for the same record.

Why are some fields empty?

Dribbble does not publish every attribute for every shot. Empty means the source did not show it, not that extraction failed.

What export formats are supported?

JSON, CSV, Excel, HTML and RSS from the Output tab, plus the Apify API and any integration you connect.

How fast is it?

It is pure HTTP with no browser, so a page of results typically takes a second or two. Raise Max concurrency carefully — the source rate-limits aggressive crawling.

Can I schedule it?

Yes. Use the Apify scheduler to run it on any interval and append each run to the same dataset for time-series analysis.

Does it work behind a proxy?

It uses Apify Proxy automatically. You can switch groups or supply your own proxies in Proxy configuration.

How often does the data change?

Dribbble updates continuously. Re-run whenever you need current data; the Actor always reads the live pages, never a cache.

Is the output schema stable?

Yes. Field names and types are fixed, so downstream pipelines will not break between runs.

What if the site changes its layout?

Open an issue on the Issues tab and it gets fixed. The Actor is actively maintained.

Is it legal?

This Actor reads only publicly available pages on Dribbble — the same content any visitor sees without logging in. It does not bypass authentication, does not collect private data and does not attempt to defeat access controls. You are responsible for how you use the output: respect the source's terms of service, applicable copyright, and data-protection law such as GDPR where personal data is involved. Scraping public data is generally lawful in the EU and the US, but the responsibility for the downstream use of that data sits with you.

Related scrapers

• Website Contact Scraper — Turn profile URLs into contact details
• LinkedIn Profile Scraper — Professional profile data
• Product Hunt Scraper — Daily product launches
• Behance-style sourcing — Bulk image and media extraction