Frequently asked questions

WolfXL Community 2.0.9 is MIT-licensed, public on PyPI, and does not need a credential or private package index. Start with the unpinned Community command:

pip install wolfxl

Commercial 2.1+ licensees receive a private, revocable credential for the authenticated WolfXL package index. That separate distribution does not gate, replace, or change the public Community package.

python -m pip install "wolfxl>=2.1" --index-url https://packages.wolfxl.com/simple/

The authenticated WolfXL index carries WolfXL and defusedxml. It does not mirror PyPI, so other packages in your project install from PyPI. On Python 3.10, WolfXL also needs tomli and typing_extensions, which install from PyPI in a separate step; the install recipes include that step.

Every person who directly installs, imports, configures, develops against, tests, or executes WolfXL as part of their work needs a seat, regardless of job title. People who only view resulting workbooks or reports do not. AI agents, CI jobs, and other automated systems you run for your organization don't need their own seats. They run under the seat of the person who sets them up.

Two ways. Install WolfXL Community from public PyPI and use it under MIT for as long as you like. To evaluate the commercial 2.1+ line, start a self-serve 30-day evaluation for a nonproduction proof of concept: same wheels, same API, no feature gates, ending automatically after 30 days.

Yes. WolfXL Community 2.0.9 is published on public PyPI under the MIT license and is the maintained 2.0 generation. Pre-launch development builds numbered below 2.0.1 are yanked and unsupported. The commercial 2.1+ line ships through the authenticated package index.

Yes. Monthly and annual buy the same license and the same wheels; only the billing interval differs. Annual saves 15% or more against paying monthly for twelve months. To switch intervals, email trial@wolfxl.com. Invoices, payment details, and cancellation are in the billing portal at https://wolfxl.com/billing.

No. We do not include telemetry, phone-home license activation, or runtime usage tracking. We rely on standard organizational compliance. Your private index credential regulates download access.

No. Confirmed correctness bugs in the supported WolfXL 2.1.0+ API are prioritized consistently for every licensed tier. Five Seats and Organization cover more people who use WolfXL, and all three plans check out online. A written Order adds OEM, redistribution, multi-entity, or negotiated service terms. No plan buys access to correctness fixes withheld from another.

WolfXL. Modify mode writes back only the parts you changed, so an edit to two cells leaves the untouched charts, drawings, styles, pivot tables, and macro code as they were. In the committed benchmark run it was the fastest full read/write library in every measured case, 2.6x to 27x over openpyxl 3.1.5.

Open it in modify mode, change the cells you need, and save. The cells you name are updated and every untouched part of the package is written back as it was. The documented structural edits are insert_rows, delete_rows, insert_cols, delete_cols, and move_range.

import wolfxl

wb = wolfxl.load_workbook("model.xlsx", modify=True)
wb["Summary"]["B4"] = 42500.0
wb.save("model.xlsx")

Yes, for a documented formula set. Native calculation ships in WolfXL Commercial 2.1+, which evaluates supported formulas in the Python process and writes fresh cached values with no Excel, no LibreOffice, and no COM automation step. The MIT-licensed Community 2.0 line includes a Python formula evaluator, wb.calculate(), that computes supported values in memory, but it does not write fresh cached values into the saved file.

WolfXL Commercial 2.1+ renders supported worksheets, cell ranges, and charts to PDF, PNG, SVG, or JPEG through a native Python API, with no GUI, no Excel install, and no LibreOffice. The MIT-licensed Community 2.0 line does not ship rendering.

For the documented subset, not as a blanket replacement. The compatibility matrix scores each surface row as supported, partial, not yet, or out of scope, so the boundary is published rather than implied, and wolfxl.install_as_openpyxl() routes existing imports in-process for the supported subset.