How to Extract XBRL & iXBRL Filings to CSV Online (SEC & Companies House)
To extract tagged financial facts from XBRL (.xbrl, .xml) or Inline XBRL (.xhtml, .htm) regulatory filings into CSV without installing Python or Arelle, parse the document locally with the EasyExtract XBRL & iXBRL Extractor. It scans every element carrying a contextRef attribute via browser DOMParser and exports Concept, ContextRef, UnitRef, and Value to CSV.
Financial regulators including the US Securities and Exchange Commission (SEC EDGAR) and UK Companies House mandate machine-readable XBRL and Inline XBRL (iXBRL) reporting for 10-K, 10-Q, and annual statutory accounts. While analysts and developers often install libraries like edgartools, ixbrl-parse, or the desktop Arelle suite to query filings, one-off extractions from downloaded filing files do not require a local Python environment.
How XBRL and Inline XBRL store financial facts
Both standalone XBRL XML instances and HTML-embedded iXBRL filings bind each reported number or category to a reporting context (period and entity) and an optional measurement unit.
| Filing Attribute | XBRL XML (.xbrl / .xml) | Inline XBRL (.xhtml / .htm) |
|---|---|---|
| Concept / Tag | Element tag name (such as us-gaap:Revenues) |
name attribute on ix:nonFraction / ix:nonNumeric |
| ContextRef | contextRef ID linking period start/end dates |
contextRef ID (falls back to lowercase contextref in HTML) |
| UnitRef | unitRef ID (USD, GBP, shares) |
unitRef / unitref attribute where numeric |
| Value | Inner text content of the XML fact node | Visible text inside the inline HTML tag (whitespace normalized) |
Any DOM element with a contextRef attribute represents an atomic financial fact. Filtering for those elements isolates reported KPIs while ignoring decorative HTML layout markup around an inline filing.
<ix:nonFraction name="uk-core:TurnoverRevenue" contextRef="FY2025" unitRef="GBP">4,820,000</ix:nonFraction>
How to extract XBRL and iXBRL filings to CSV online
- Download the instance
.xml,.xbrl, or inline.htm/.xhtmlfile from SEC EDGAR or Companies House. - Open the EasyExtract XBRL & iXBRL Extractor in any browser and drop the filing onto the dropzone.
- Inspect the parsed preview table listing Concept/Tag, ContextRef, UnitRef, and Value (up to 500 preview rows; XML errors automatically fall back to HTML DOM parsing for messy iXBRL markup).
- Click Download CSV to export
xbrl-facts.csv, or copy the table directly into Excel or Google Sheets.
When to use a browser extractor vs Python or Arelle
Browser extraction excels when you want instant tabular inspection of an individual filing on a locked-down work laptop or Chromebook without installing dependencies. When automating bulk downloads across thousands of SEC EDGAR CIKs or validating taxonomy calculation linkbases, Python packages such as edgartools, stream-read-xbrl, or Arelle remain the right programmatic pipeline.
Frequently asked questions
Why does the extractor skip paragraphs longer than 500 characters?
Inline XBRL filings sometimes wrap multi-page HTML accounting policy footnotes inside ix:nonNumeric tags. Skipping text blocks over 500 characters keeps numeric financial CSV exports clean and readable in Excel.
Are pre-filing financial reports uploaded to a server?
No. Parsing executes strictly inside your browser’s local JavaScript memory using DOMParser, so confidential financial disclosures never leave your device.
Does this handle HTML filings that fail strict XML parsing?
Yes. The parser tries text/xml first and automatically falls back to text/html parsing if an inline filing contains HTML entities or unclosed tags.
Related structured data and financial tools
- XML Field Extractor: Query custom XPath-like tags and attributes from any XML file.
- CAMT.053 to CSV Converter: Convert ISO 20022 XML bank statements to CSV.
- Excel Data Extractor: Export sheets from XLSX workbooks into clean CSV.
- CSV Column Extractor: Filter specific columns from exported XBRL CSV tables.