-Note: as mentioned in the README, wimlib generally provides a slightly better
-XPRESS compression ratio than Microsoft's software, while it generally provides
-a slightly worse LZX compression ratio than Microsoft's software. So, you may
-not want to specify \fB--recompress\fR when optimizing a LZX-compressed WIM
-created on Windows with Microsoft's ImageX.
+Note: as of wimlib v1.5.3, wimlib's LZX compressor usually achieves the same or
+better compression than Microsoft's, but is slightly slower.
+.TP
+\fB--recompress-slow\fR, \fB--compress-slow\fR
+Spend even more time compressing the data in order to achieve a more optimal
+compression ratio. Compared to the default \fB--recompress\fR, this will make
+compression about twice as slow and will increase the compression ratio by maybe
+1%, depending on the data. This option implies \fB--recompress\fR and
+\fB--compress\fR=\fImaximum\fR (recompress using LZX compression).
+.TP
+\fB--compress\fR=\fITYPE\fR
+Recompress the WIM file using the specified compression type. \fITYPE\fR may be
+"none", "fast", or "maximum". This implies \fB--recompress\fR.
+.TP
+\fB--chunk-size\fR=\fISIZE\fR
+Set the WIM compression chunk size to \fISIZE\fR. Using this option is not
+recommended because WIM chunk sizes other than the default of 32768 are not
+supported by Microsoft's software. But if you decide to use this option
+regardless, you can choose a chunk size that is any power of 2 greater than or
+equal to 2^15 (32768) up to 2^21 (2097152) for LZX ("maximum") compression or
+2^26 (67108864) for XPRESS ("fast") compression. Larger chunks mean larger LZ77
+dictionaries and better compression ratios on sufficiently large files, but
+slower random access.