Is openpyxl still worth learning for Excel automation and freelance work?

Learn it, but understand its limits. It’s a good fit for ordinary-sized files and workbooks where you need to inspect or modify individual cells, ranges, formulas, styles, named ranges, or worksheet structure. For very large files or performance-sensitive ingestion, tools such as Polars, DuckDB, fastexcel, or calamine may be faster. Those are alternatives for specific workloads, not evidence that openpyxl is obsolete.

Also consider the client’s environment before choosing the technology. Power Query or VBA can sometimes be easier for Excel users to maintain, while Python is better suited to backend automation and repeatable data pipelines. If you need Excel itself to calculate features or preserve more of the application’s behavior, xlwings can be useful, but it requires Windows and an installed copy of Excel. For portable .xlsx file manipulation, openpyxl is usually the simpler option.

Yes, it’s still very relevant. The “Excel 2010” wording mostly refers to the XLSX format introduced around that time. That format is still widely used, and openpyxl remains useful for reading and writing workbooks, editing cells, applying styles, setting column widths, freezing panes, adding formulas, and generating polished reports. Pandas also commonly relies on it when working with modern .xlsx files.

Excel is still deeply embedded in business, especially in finance, HR, operations, and reporting. For freelance automation, the ability to manipulate the actual workbook—not just export a plain table—is valuable. Many clients want a finished spreadsheet with specific formatting, formulas, multiple sheets, and a familiar workflow. Openpyxl is a practical choice for that kind of work and is easy to deploy when the client doesn’t have Excel or Python installed.