Naver Webtoon Scraper 🇰🇷📚

Scrape Naver Webtoon (네이버 웹툰) — Korea's #1 webtoon platform and the birthplace of global hits like Lookism, Tower of God and True Beauty. Get the weekday lineup rankings and the completed-series catalog as clean, structured JSON (title, author, weekday, user star rating, new/hiatus/completed flags, thumbnail, URL — plus cumulative view counts on the completed catalog), exportable to JSON, CSV, or Excel.

Webtoons are Korea's fastest IP pipeline: today's top-rated weekday title is tomorrow's Netflix drama or feature film. This actor gives you that catalog as data.

Try it free. Apify's free plan includes $5 of monthly platform credit — roughly 2,000 results from this actor, no credit card required. Set your input, click Start, and export JSON/CSV/Excel.

---

🚀 What it does

Give it a mode and it returns a structured webtoon catalog:

Mode	What you get	Example input
weekday	The current weekly lineup — every ongoing title on the Mon–Sun tabs (or a single tab), ranked in your chosen order	{ "mode": "weekday" }
completed	The finished-series catalog (~3,000 completed titles), paginated — with full cumulative view counts when sorted by views	{ "mode": "completed", "order": "view" }

Choose a weekday (all, mon…sun, or the dailyPlus daily-webtoon tab), a sort order (user rating, view count, update recency) and how many titles to pull (maxItems).

---

📥 Input

Field	Type	Default	Description
mode	string	weekday	weekday (weekly lineup) or completed (finished-series catalog).
week	string	all	Weekday tab: all (Mon–Sun in one request), mon…sun, or dailyPlus (매일+ daily webtoons). Weekday mode only.
order	string	user	user (star rating), view (cumulative views), update (latest update).
maxItems	integer	200	Max titles to return. Full weekly lineup ≈ 780 rows; completed catalog ≈ 3,000 titles.
proxyConfiguration	object	off	Optional Apify proxy. Not required — the API is datacenter friendly; enable for IP diversity at scale.

Input example — the full weekly lineup, top-rated first:

{
  "mode": "weekday",
  "week": "all",
  "order": "user",
  "maxItems": 800
}

---

📤 Output

Each webtoon is one dataset record in this shape (real samples from live runs):

{
  "source": "naver_webtoon",
  "title_id": "758037",
  "title": "참교육",
  "author": "채용택 / 한가람",
  "weekday": "mon",
  "rank": 1,
  "rating": 9.9,
  "view_count": null,
  "is_new": false,
  "is_rest": false,
  "is_up": false,
  "is_adult": false,
  "is_completed": false,
  "url": "https://comic.naver.com/webtoon/list?titleId=758037",
  "thumbnail_url": "https://image-comic.pstatic.net/webtoon/758037/thumbnail/thumbnail_IMAG21_6323d62f-2b2d-4668-9373-156f16487568.jpg",
  "scraped_at": "2026-07-10T15:21:02.382+09:00"
}

A completed + order: "view" record additionally carries the lifetime view count:

{
  "source": "naver_webtoon",
  "title_id": "325629",
  "title": "패션왕",
  "author": "기안84",
  "weekday": null,
  "rank": 2,
  "rating": 8.34,
  "view_count": 366878225,
  "is_completed": true,
  "url": "https://comic.naver.com/webtoon/list?titleId=325629"
}

Field notes

• author — the public pen-name credit shown on every webtoon card (writer / artist / original author, e.g. 채용택 / 한가람). This is commercial authorship attribution, like an artist name on an album — no personal profiles, IDs, or contact details are collected.
• weekday — mon…sun or dailyPlus for the lineup; null for the completed catalog. A title serialized on several days appears once per day (that is the lineup).
• rank — 1-based position in the chosen ordering, per weekday tab (weekday mode) or across the catalog (completed mode).
• rating — user star rating, 0–10 scale (e.g. 9.9).
• view_count — lifetime views. Fully populated only in completed mode with order: "view"; elsewhere the API hides the number for most titles and the field is null (see Known limitations).
• is_new / is_rest / is_up — new series, on hiatus (휴재), episode updated.
• is_adult — age-restricted (19+) flag; is_completed — series has ended.
• A 40-record real sample (both modes) lives in samples/sample-output.json.

---

💡 Use cases

• Webtoon IP & adaptation scouting — webtoons are the source material for Korea's drama/film pipeline. Rank the lineup by user rating or views and spot adaptation candidates before they are optioned.
• Content market research — track lineup composition by weekday, new-series inflow (is_new), hiatus rates (is_rest), and completed-catalog performance over time.
• Trend tracking — schedule daily runs and diff the rankings: rising titles, rating moves, lineup entries and exits.
• Fan tooling — build update notifiers, reading lists, or catalog browsers on clean JSON instead of scraping HTML.
• AI agents & LLM pipelines — feed a structured catalog of Korea's #1 webtoon platform into RAG or a content-analysis assistant.

---

🌐 Data source

This actor reads Naver Webtoon's public titlelist API on comic.naver.com — the same JSON endpoints the site's own weekday tabs and completed-catalog pages call. No login, no private API, no HTML parsing. The API is datacenter friendly, so no proxy is required; you can enable an Apify proxy for IP diversity when running at scale.

---

⚠️ Known limitations (honest notes)

• view_count is only fully populated in completed mode with order: "view". The weekday endpoint sorts by views but exposes the actual number for only a couple of titles per weekday — all hidden values are emitted as null, never fake zeros.
• The completed catalog can include a few long-hiatus titles. Naver lists some indefinitely-paused series in its finished tab; they come through with is_completed: false / is_rest: true, exactly as the API flags them.
• No genre or synopsis fields. The titlelist API does not return genre labels or descriptions, so they are not advertised here. Per-episode data and reader comments are out of scope (comments are personal data and are never collected).

---

⚖️ Rate & legality note

• Only public, non-personal catalog data is collected — the same lineup anyone sees on comic.naver.com without logging in. No personal data: no reader comments, nicknames, or profiles (the actor never calls comment endpoints), and the API's internal author-id / personal-blog sub-fields are deliberately dropped. author is the public pen-name credit, like an artist name on an album.
• Requests are rate-limited (sequential requests, ≥500 ms delay) to stay light on the site — a full weekly lineup is a single API call.
• You are responsible for complying with Naver's Terms of Service and applicable law in your jurisdiction. Use the data for research, monitoring, and analytics — not to replicate the platform or redistribute the comics themselves.

---

❓ FAQ

Is it legal to scrape this data? This actor collects only public, non-personal catalog data — the same weekday lineup and completed list any visitor sees on Naver Webtoon without logging in. No reader data or personal information is collected. You are responsible for how you use the data; see the rate & legality note above.

What does it cost in practice? $2.50 per 1,000 results (launch pricing) + a few cents of platform usage. Example: the full weekly lineup (~780 rows) costs about $1.95 per snapshot. Apify's free $5 monthly credit covers ~2,000 results.

Do I need to configure proxies? No — the default settings work out of the box. Optionally, enable an Apify proxy for IP diversity when running at scale.

How fresh is the data? Every run scrapes the live Naver Webtoon API at run time. Schedule the actor daily to build a rankings time series.

What is NOT included? Reader comments and any reader/user data (never collected), genre/synopsis (not exposed by the titlelist API), per-episode lists, and view_count outside completed + order: "view" (emitted as null, see Known limitations).

---

🇰🇷 More Korean data actors

This actor is part of a suite of Korean-platform scrapers by the same maintainer:

• ktown4u-scraper — K-pop albums & goods from the global fan commerce leader.
• pocamarket-scraper — K-pop photocard marketplace listings & prices.
• tumblbug-scraper — Korea's creative crowdfunding platform, project & funding data.

Browse all: apify.com/kdatafactory

---

🏃 Run it

On Apify: set your input and click Start. Locally:

npm install
# put your input in storage/key_value_stores/default/INPUT.json
npm start

Results land in the default dataset (Apify) or ./storage/datasets/default (local).

---

If this actor saves you time, a rating on the Store page helps a solo maintainer a lot. Found an issue? Open it in the Issues tab — I respond fast.