Skip to content

Ripping CDs


Check out dbPoweramp's CD Drive Accuracy 2024 Report if you are looking for a good drive to rip CDs with.

Rip logs, usually with the extension .log, are status report files produced by CD ripping software. They describe what settings a particular CD was ripped with and contain information about any errors that occurred during the ripping process. This gives an idea of how likely the extracted data is accurate to the data on the CD.

Rip logs are scored by log checkers, which can be found on private trackers. One of the private tracker's logchecker is also available on GitHub at OPSnet/Logchecker. We also host our own logchecker, Cambia, which has support for more log types than other checkers, multiple scoring systems soon and more accurate log parsing logic. When a rip scores 100% a [100%LOG] tag should be added to the folder or zip name when sharing.

If a rip scores less than 100% the configuration of the ripper should be rechecked. If the problem persists, the issue might be with the disc itself (dirty, scratched, degraded, etc) in which case cleaning the disc and reripping before switching to another ripper as a last resort is the way to go.

Each ripper should only be used on their respective platforms. Some communities don't acknowledge Whipper logs, in that case consider finding a Windows machine or dual booting.

Known and respected rippers for all platforms:

Guides for ripping with them:


  • Using rippers that don't produce scoreable logs or aren't widely used should be avoided as they are likely to alter the audio in unforeseen ways, not count for all variables during ripping and not perform thorough error checks.
  • Do not use any software with CD ripping as a secondary feature to rip discs.


  • People tend to confuse track quality and peak level in the log text with the actual log score. They are not the same. Track quality and peak level are not used during scoring.
  • Logs can be forged but the effort required usually bars people from doing so.


  • A 100% log does not guarantee that the data is accurate. It should be interpreted as "very likely to be accurate judging by the info in the log" but not as "100% accurate".

Salty | Created 2021/10/04 | Updated 2022/03/10