Arelle
Table of Contents
Description
Arelle is an end-to-end open source XBRL platform, which provides the XBRL community with an easy to use set of tools. It supports XBRL and its extension features in an extensible manner. It does this in a compact yet robust framework that can be used as a desktop application and can be integrated with other applications and languages utilizing its web service, command line interface, and Python API.
Documentation
Need help with Arelle? Go check out our documentation.
Features
- Fully-featured XBRL processor with GUI, CLI, Python API and Web Service API.
- Support for the XBRL Standard, including:
- XBRL v2.1 and XBRL Dimensions v1.0
- XBRL Formula v1.0
- Taxonomy Packages v1.0
- xBRL-JSON v1.0 and xBRL-CSV v1.0
- Inline XBRL v1.1
- Units Registry v1.0
- Certified by XBRL International as a Validating Processor.
- Support for filing programme validation rules:
- Edgar Filer Manual validation (US SEC)
- ESEF Reporting Manual (EU)
- HMRC (UK)
- CIPC (South Africa)
- FERC (US Federal Energy Regulatory Commission)
- Integrated support for Arelle Inline XBRL Viewer.
- Extensible plugin architecture.
- Support for XF text-based Formula and XULE validation rules.
- The Web Service API allows XBRL integration with applications, such as those in Excel, Java or Oracle.
- Instance creation is supported using forms defined by the table linkbase.
- Support for reading/monitoring US SEC XBRL RSS feeds (RSS Watch).
Need Support?
Whether you've found a bug, need help with installation, have a feature request, or want to know how to use Arelle, we can help! Here's a quick guide:
When reporting issues it's important to include as much information as possible:
- what version of Arelle are you using?
- how are you using Arelle (GUI, command line, web server, or the Python API?)
- what operating system (Windows, macOS, Ubuntu, etc.) are you using?
- what plugins if any do you have enabled?
- can you provide an XBRL report that recreates the issue?
- what's the diagnostics output (
arelleCmdLine.exe --diagnostics) on your system?
Arelle Within Other Products
A number of service providers embed Arelle within their XBRL products and tools. If you're having an issue with Arelle within one of these offerings please contact the developer of that tool for support or first verify that you have the same issue when using Arelle directly. Most issues in these situations are caused by the tool using an old version of Arelle or not running a valid command.
EDGAR or EFM Validations
The SEC develops and maintains the EDGAR plugins. Please report issues with these plugins directly to the SEC (StructuredData@sec.gov).
Installing or Running Arelle
Most installation and startup issues can be resolved by downloading the latest version of Arelle and performing a clean install. If that doesn't resolve the problem for you, please report a bug.
Bug Report or Feature Request
Please use the GitHub issue tracker if you'd like to suggest a new feature or report a bug.
Before opening a new issue, please:
- Check that the issue has not already been reported.
- Check that the issue has not already been fixed in the latest release.
- Be clear and precise (do not prose, but name functions and commands exactly).
- For bug reports include the version of Arelle you're using.
Security Vulnerabilities
Identified a security concern? Email the Arelle team (Support@arelle.org) so we can resolve the issue and make sure service providers and authorities who use Arelle in production are prepared to update and apply security patches before notifying the general public.
How-To and General XBRL Questions
Have a question that isn't covered by the documentation? Join our Arelle Google Group and start a conversation with the Arelle team and community of experts.
The Arelle team can also be reached by email (Support@arelle.org) for issues that aren't a good fit for the other support channels. However, please note that you will likely receive a faster response if you open a GitHub issue or start a new conversation in the Arelle Google Group where the Arelle team is active and other people within the community can also see and respond to your message.
How To Contribute
Interested in contributing to Arelle? Awesome! Make sure to review our contribution guidelines.
👥 Contributors
Join our community and become a contributor today! 🚀
License
2 maintainers
Metadata
2 maintainers
Release files for arelle-release 2.46.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| arelle_release-2.46.1.tar.gz | 5.7 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| arelle_release-2.46.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.9 MB
Release files / arelle_release-2.46.1.tar.gz
| Download URL | arelle_release-2.46.1.tar.gz |
|---|---|
| Size | 5.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d2c5942448f1c1a38370410da4998badb23db1d8bf38cce1b4d075a222e1244d
|
|
BLAKE2b-256 checksum How to use checksums |
a0e40d838db7197b4b48a3e8023c6e9c06f2762fda3097de5e18fd38d6af7a5e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.
Transparency logRelease files / arelle_release-2.46.1-py3-none-any.whl
| Download URL | arelle_release-2.46.1-py3-none-any.whl |
|---|---|
| Size | 6.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
87a5369913471afa02d6d464d48a04a20acc073cc1df1fdaaae14d8b7b5229d0
|
|
BLAKE2b-256 checksum How to use checksums |
dd8e6d40c41bc82970dd28d595b0204cd93f19bfc6c5e28a08165cc00bc28606
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.
Transparency log
