wikiextractor/wikiextractor

A tool for extracting plain text from Wikipedia dumps

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 2 minutes ago
Added to GitGenius on September 17th, 2026
Created on March 22nd, 2015
Open Issues & Pull Requests: 96 (+0)
GitHub issues: Enabled
Number of forks: 1,000
Total Stargazers: 4,004 (+0)
Total Subscribers: 68 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 153.5 days
Mean response time: 710.0 days
90th percentile: 1868.9 days
Tracked items: 65

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 17
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 603 days
Stale 30+ days: 15
Stale 90+ days: 4

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

WikiExtractor is a Python tool for extracting and cleaning plain text from Wikipedia database backup dumps.

The tool solves the problem of converting raw Wikipedia XML dumps into usable plain text by preprocessing the entire dump to extract and expand template definitions, then processing articles in parallel using multiprocessing. A cache of parsed templates is maintained to speed up repeated extractions. The tool offers a `--no-templates` option that significantly accelerates processing by skipping template expansion entirely, and a separate Cirrus Extractor variant that works with pre-expanded Cirrus dumps from the cirrussearch repository.

WikiExtractor requires only Python 3 with no additional library dependencies, making it straightforward to deploy. It suits projects that need to bulk-process Wikipedia content for natural language processing, machine learning training data, or text analysis. The tool can be invoked directly as a script or installed via package managers. Output is distributed across multiple files of similar size in a specified directory, each containing documents in a structured format. Users working with large dumps should consider whether template expansion is necessary for their use case, as disabling it provides substantial performance gains.

Issues and pull requests often wait weeks or longer for a first response.