read this first (faq)

about pingo
  • it is speed/space based — it will not provide maximum compression
  • pingo could adjust quality by itself whatever the lossy option
  • pingo has quality limitations because lower will be probably bad
  • if you want help about how pingo works — read usage
  • for maximum performance, use pingo alone and not throught a front-end/batch
  • you should not use throught single/multithreading: pingo does this by itself
  • it seems to work on Linux (using wine)
  • i do not provide any other tool than pingo
  • i do not make custom build or provide older version
  • 64-bit: compatible with 64-bit system only — recommended (speed/memory)
  • 32-bit: compatible with 32/64-bit system
  • there is no roadmap — no previsions — no dates
  • i could not guarantee that the tool works correctly
  • use only on backup and test files. always do backup!
bugs report
  • i am interested to fix bugs in current version (not older)
  • be sure you are using the latest version of pingo
  • it could help if you do trials yourself — if it bugs on a file, provide it
  • do NOT test pingo throught another tool — test pingo itself directly on files
  • please do report with all informations (version, bit-version, options, OS, files, etc.)
  • you read everything, now here is the way to contact me
other techs
  • those techs are not used in pingo
  • Guetzli — mainly because of speed (see comparisons)
  • Lepton — which is a JPG packer, not an optimizer (see PackJPG)