Who still asks for a BMP
Almost nothing modern wants BMP, and yet the requests keep coming: industrial control panels, point-of-sale terminals, embedded display firmware, machine-vision software, and in-house Visual Basic or Delphi applications written before PNG decoding was a given. Those programs read raw bitmaps because raw bitmaps need no decoder at all. If a piece of equipment or a decades-old tool rejects your PNG, converting it is usually faster than arguing with the vendor.
What the converter writes
The output is an uncompressed 32-bit BMP: a short header followed by raw pixel rows, bottom to top, four bytes per pixel. Nothing is compressed and nothing is resized, so the file size is pure arithmetic — width times height times four, plus the header. A 64×64 image lands around 16 KB no matter how small the PNG was, and a 1920×1080 screenshot comes out near 8 MB. Growing by an order of magnitude is normal here and is not a sign that something went wrong.
Transparency, and when to skip this
PNG transparency does not survive in a form old software understands, so transparent areas are flattened onto a white background before the bitmap is written — left alone they would come out black in most readers. Keep that in mind for logos with cut-out backgrounds. Because BMP costs so much in file size and gives nothing back in quality, it is only worth producing when something on the other end genuinely demands it; for storage, sharing, or the web, the PNG you already have is the better file. Conversion runs in a Web Worker on your device, batches move three at a time, and results download individually or as a ZIP.