The Problem (Q-score 3, ranked #293rd of 303 in the Excel VBA archive)
The scenario as originally posted in 2009
Which is better API for excel parsing in Java Apache POI or JExcel API?
In terms of speed, memory utilization and code stability.
Why community consensus is tight on this one
Across 303 Excel VBA entries in the archive, the accepted answer here holds niche answer (below median) status — meaning voters are unusually aligned on the right fix.
The Verified Solution — niche answer (below median) (+7)
Advisory answer — community consensus with reference links
Note: the verified answer below is a reference / advisory response rather than a copy-ready snippet.
Personally I would recommend POI over JExcel. The reasons I chose POI over JExcelAPI are:
- POI supports both old and new MS Excel sheet formats
- It has a cleaner API (imho)
- As far as I can see it does not suffer from the irritating DateTime issues that JexcelApi has (Date display).
I have had the opportunity to use both. POI, in my opinion, has a really well thought out and easy to use API. The biggest benefit from my perspective is that you can factory off the creation of the worksheet instance and then deal with everything in the context of the usermodel interfaces. This means your code can process both old and new Excel file formats without having to worry about which is which.
Additionally, you are able to read and write the same Worksheet instance. With JExcelApi there is this really strange split between “readable” sheets and “writable” sheets which I found odd. This also resulted in me having to introduce messy work arounds to move from “reading” to “writing” in my code.
I did not notice meaningful performance difference using POI on old, binary files (POI HSSF) and JExcelApi. There is however a significant performance difference between POI HSSF (old format) and POI XSSF (new format). I assume this is because of all the extra work required for unpacking and parseing XML.
When to Use It — vintage (14+ years old, pre-2013)
Ranked #293rd in its category — specialized fit
This pattern sits in the 98% tail relative to the top answer. Reach for it when your scenario closely matches the question title; otherwise browse the Excel VBA archive for a higher-consensus alternative.
What changed between 2009 and 2026
The answer is 17 years old. The Excel VBA object model has been stable across Office 2013, 2016, 2019, 2021, 365, and 2024/2026 LTSC, so the pattern still compiles. Changes that might affect you: 64-bit API declarations (use PtrSafe), blocked macros in downloaded files (Mark-of-the-Web), and the shift toward Office Scripts for web-first workflows.