Naver Webtoon Scraper

What does Naver Webtoon Scraper do?

Naver Webtoon Scraper reads public listing pages on Naver Webtoon. It collects each visible series card once per titleId and keeps the first observed list position and section. When the same title appears in recommendation and full-list sections, its output record retains both section appearances and their positions.

The Actor keeps the existing Playwright crawler and weekday or genre browse modes. Its records can include visible title, creator credits, numeric rating, thumbnail, short card labels, selected sort tab, source section, and a latest-episode label when one is present. It does not fetch episode detail pages.

Why use Naver Webtoon Scraper?

Use the structured dataset to review public series listings, compare ratings, track visible card labels, or identify the series highlighted in a recommendation section. Naver Webtoon may display multiple cards for one series on a page; the Actor deduplicates those appearances by numeric titleId while preserving their order and section context.

Runs use the Apify Actor interface, so you can start them in the Console, schedule them, retrieve datasets through the API, and inspect run history. The existing Actor can use the configured Apify Proxy settings. Proxy use does not guarantee that Naver Webtoon will serve a page.

What data can it extract?

Group	Fields	Meaning
Identity and order	recordType, position, title, titleId, link	Webtoon card identity and first-observed output order.
Section and page	sourceUrl, sourcePageTitleLinkCount, sourcePageUniqueTitleCount, sourceSection, sectionType, sectionPosition, sectionPositions, sectionAppearances, isRecommended, isInAllSection	Source page, visible link and unique-title counts, section heading, per-section positions, and whether the title appeared in the observed sections.
Sort and weekday	selectedSortLabel, availableSortLabels, weekday, weekdayCode, weekdayLabel	Visible sort controls and configured weekday context. Sort labels are read from the page; there is no sort input.
Creators and rating	author, artist, creatorCredits, creatorNames, starScore, starScoreLabel	Visible slash-separated credits and numeric rating in both numeric and displayed-text forms.
Card content	thumbnail, rawLabels, latestEpisodeLabel, summary, ageRating, genre	Visible card values when present, plus the configured genre label in genre mode. Labels are preserved as displayed and are not assigned extra meanings.
Provenance	extractionMethod, scrapedAt	DOM extraction method and record time.

Missing optional values are omitted. The optional latest episode value is a card label such as 140화; the Actor does not crawl the episode itself.

How to scrape Naver Webtoon

1. Open the Actor's Input tab.
2. Choose weekday mode and a weekday such as mon, or choose genre mode and one of the listed genres.
3. Set maxItems from 1 to 500. The default is 50.
4. Configure Apify Proxy settings only if they are appropriate for your run.
5. Start the Actor and inspect its dataset.

A minimal Monday input is:

{
  "mode": "weekday",
  "weekday": "mon",
  "maxItems": 50
}

A genre input using the existing input contract is:

{
  "mode": "genre",
  "genre": "ACTION",
  "maxItems": 100
}

How much will it cost to scrape Naver Webtoon?

There is no fixed price per series. The run uses Apify compute and browser time, so its cost depends on the selected item limit, page loading time, any pagination exposed by the listing page, retries, and proxy configuration. Start with a smaller maxItems when checking a new input, then use the run's compute and usage details to estimate larger runs. This Actor does not open a detail page for each webtoon.

Input

See the Input tab for the complete configuration.

Field	Type	Default	Description
mode	string	weekday	Browse by weekday or genre.
weekday	string	mon	One of mon, tue, wed, thu, fri, sat, or sun. Used in weekday mode.
genre	string	PURE	One of COMIC, FANTASY, ACTION, DAILY, PURE, DRAMA, THRILLER, SPORTS, or HISTORICAL. Used in genre mode.
maxItems	integer	50	Maximum unique title IDs to emit, from 1 to 500.
proxyConfiguration	object	—	Optional Apify Proxy configuration for the crawler.

The page's selected sort tab is observed from the rendered controls. The Actor does not switch sort tabs through input.

Output

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

The following is an excerpt of the parent-observed Chrome page, not Actor output. The card details are only the values supplied from the visible Monday listing; page-level observations are shown separately where they were not tied to that specific card.

{
  "pageUrl": "https://comic.naver.com/webtoon?tab=mon",
  "sections": ["추천 월요웹툰", "전체 월요웹툰"],
  "sortTabs": {
    "selected": "인기순",
    "visible": ["인기순", "업데이트순", "조회순", "별점순"]
  },
  "observedCardExcerpt": {
    "title": "신체",
    "titleId": 844058,
    "creatorCredits": "엄세윤 / 정썸머",
    "starScore": 9.83
  },
  "otherVisibleRawLabels": ["UP", "휴재", "신작", "청유물"],
  "recommendationEpisodeLabelExamples": ["140화", "16화", "12화"],
  "sourcePageTitleLinkCount": 262
}

The Chrome excerpt above documents the supplied browser observation. It is not a sample Actor run or a claim that those values were returned by an Actor execution. In the dataset, the schema separates the first observed section from any later section appearances for the same titleId.

Tips and advanced options

• Use maxItems to cap the number of unique title IDs emitted.
• The Actor follows a visible next-page control when the listing page exposes one.
• The first appearance determines position, sourceSection, and sectionPosition; later appearances add to sectionAppearances and sectionPositions.
• Sort metadata reflects the currently selected page tab; the Actor does not accept a sort choice as input.
• Raw labels such as UP, 휴재, 신작, and 청유물 are returned as visible text. The Actor does not reinterpret them as availability, maturity, or publication claims.
• Long page loads or access restrictions can reduce available results. The Actor does not solve challenges or follow prompts displayed by the site.

FAQ, support, and responsible use

Why are some fields missing? Card fields are optional and are included only when a matching visible value is available. Recommendation-only latest episode labels may be absent from other cards.

Why does one title contain multiple section positions? Naver may show a title in more than one section. The dataset keeps one row per titleId and records each distinct observed section and position.

Does the Actor return an episode list? No. It can capture a visible latest-episode label, but it does not visit episode or detail pages.

For troubleshooting, use the Actor's Issues tab and include the run ID and a short description. The Actor is not affiliated with Naver. Use it only with public information and follow Naver's terms, applicable rate limits, and local law. Public creator names and other listing content remain subject to the rules that apply to your use.