How can you tell how much CFM (MAX 10 device family) your compressed .pof file takes up if the generated file size is not indicative of the compression ratio?

Sorry, as I’m re-reading my question, I realize how poorly worded it was that I asked “how much space it takes up” – which led to the datasheet answer which I already had access to and isn’t what I really am looking for. My .pof file sizes are 321,800, according to my operating system, for either a target 10M04 or a 10M08, and regardless of my use of memory initialization files, regardless of my selection of “generate compressed bitstream” in device options, etc. Clearly a file that is 321,800 bytes (321.8KByte) is not fitting in a memory that is 2,240Kbit. Therefore, the compression that is going on is hidden / obscured from the designer. My problem is that I have a customer requirement that I not exceed 50% utilization of the memory store. Mathematically, I can’t prove that to them with these numbers. Is there any way to get the compressed image size in bits or bytes to satisfy my customer requirement? Thanks!

Also, on the illustration in Table 2, I don’t see how the uncompressed image size (321.8KB *8b/B = 2574.4Kb) fits in any of these configurations:

CFM0 = 70 pages * 16Kb = 1120Kb (supposedly fits a single compressed image)

CFM0 + CFM1 = 70+29 = 99 pages * 16Kb = 1584Kb (supposedly fits a single uncompressed image)

CFM0 + CFM1 + CFM2 = 70+29+41 = 140 pages * 16Kb = 2240Kb (supposedly fits a single uncompressed image with memory initialization)