Mutation proof
The requested cells, formulas, tables, or ranges contain the intended result.
Edit in place
How do I edit an existing Excel file in Python without losing formatting?
Open the workbook with load_workbook(path, modify=True), change the cells, and save. WolfXL modify mode edits the .xlsx in place: it writes the cells you change and retains styles, charts, pivots, and other unrelated source parts, subject to the published compatibility boundaries. For a macro-enabled .xlsm, pass keep_vba=True to retain its VBA project. openpyxl keeps the cell styles it models and rebuilds the rest of the file from what it understood. Its own tutorial warns that shapes will be lost from existing files that are opened and saved, and its reader warns that unsupported worksheet extensions, including newer data validation, conditional formatting, sparklines, and slicers, will be removed.
Make the smallest supported edit
from wolfxl import load_workbook
workbook = load_workbook("report.xlsx", modify=True)
workbook["Summary"]["B4"] = 42
workbook.save("report-updated.xlsx")
workbook.close()The saved copy keeps the source styles, number formats, and conditional formatting, because modify mode rewrites the changed cells and carries the untouched parts across. For a macro-enabled template, add keep_vba=True and keep_links=True to retain VBA and external-link package parts where the selected workflow supports them. Start with a copy of the source workbook and compare the exact parts that matter before replacing the current production path.
Where full rewrites become risky
Template-driven workbooks can combine pivots, slicers, charts, drawings, macros, external links, controls, protection, and cached formula results. A library may understand the requested cell edit while lacking full support for every surrounding package part.
openpyxl's own documentation warns that unsupported shapes can be lost when an existing file is opened and saved. That makes preservation an explicit workflow requirement rather than an incidental implementation detail.
One cell edit, measured
A worksheet with a list data validation stored as an Excel 2010 extension and a sparkline, then one edit to cell A1 on the same sheet, saved by each library on 2026-09-25:
- openpyxl 3.1.5 warned
Data Validation extension is not supported and will be removedandSparkline Group extension is not supported and will be removed. The saved file contained neither. - WolfXL with
modify=True, both the free Community 2.0.2 release and Commercial 2.1.0, saved the new A1 value and kept both the validation and the sparkline.
This shows one extension pair on one sheet. Test the parts your own templates depend on before switching a production path.
WolfXL's bounded approach
- Inspect the workbook before mutation.
- Open existing OOXML workbooks in modify mode for supported targeted edits.
- Keep external links or VBA package parts when the selected workflow and options support them.
- Write to a new output path during validation.
- Compare the parts that must remain stable before production rollout.
Evidence required for a real workflow
Package proof
Relevant relationships and source parts remain present and structurally valid.
Consumer proof
The saved file opens and behaves correctly in the application or service that consumes it.
Start with the workbook inventory
Run the local scanner first, then compare each flagged feature with the compatibility matrix and known limitations. A clean inventory still requires a bounded save-and-open proof for the exact operation.
Turn one template into an acceptance contract
A Production Workbook Pilot defines the allowed mutation, required preservation checks, deployment environment, and recovery path before implementation begins.
Scope a preservation pilot