InfraRecorder 64-bit vs 32-bit: Which Build Should You Use?

InfraRecorder 0.53 ships in real 32-bit and real 64-bit builds — the 64-bit program is genuinely native, not a repackaged 32-bit binary. The choice is not about speed. It is about one documented codec difference that can matter for audio, and this guide makes the decision simple.

First, the facts both builds share. They are the same final version, 0.53 from 1 September 2012, with the same feature set: data, audio and mixed-mode projects, ISO and BIN/CUE image burning, dual-layer DVD support, disc copying, rewritable-disc erasing, and saving tracks to WAV, WMA, OGG and ISO, with MP3 encoding available through the separate plug-in. Both are free software under GPL version 3, both list Windows 2000, XP, Vista and 7 as the official systems, and neither can burn Blu-ray. You can get either build from our download page, which links to the verified SourceForge files.

Proof the 64-bit build is native

We inspected the verified official packages directly. The 32-bit portable program, infrarecorder.exe, is a PE32 (i386) executable. The 64-bit portable program is a PE32+ (x86-64) executable — the Windows format for native 64-bit programs. The 64-bit installer, ir053_x64.msi (4,153,344 bytes, SHA-256 332704763605252ef9e88d2a8ce6d076719f0acb307db231069483ae5ca407ff), is likewise a genuine x64 package. So if a site claims the 64-bit edition is fake, that claim is wrong. If a site claims 64-bit makes burning faster or adds features, that claim is also wrong — the practical difference lies elsewhere.

The one difference that matters: libsndfile on x86 only

The 32-bit build bundles libsndfile support — in the portable package you can see libsndfile-1.dll and codec files including sndfile.irc, vorbis.irc and wma.irc in its codecs folder. The 64-bit portable codecs folder contains vorbis.irc, wave.irc and wma.irc only: no libsndfile. Libsndfile is a library for reading and writing sampled audio files, so its absence means some audio decoding paths available to the 32-bit build are not available in the same way on 64-bit. Historical user reports specifically describe MP3 decoding as problematic in the x64 build.

Be precise about what this does and does not mean. It does not mean the 64-bit build cannot make audio CDs at all, and it does not affect plain data burning or burning a finished ISO image, where no audio decoding is involved. It means that if you feed varied audio files into an audio project, the 32-bit build has the broader, better-tested decoding path. Separately, do not confuse decoding with the MP3 encoding plug-in: the plug-in adds lame.irc so you can save audio tracks as MP3, and it ships in versions for both builds.

Recommendation logic

  • Choose 32-bit if you burn audio CDs from MP3 or mixed source formats, if you are troubleshooting a track that will not add or decode, or if the target PC might be 32-bit Windows. The 32-bit installer ir053.exe and the 32-bit portable both run on 64-bit Windows.
  • Choose 64-bit if your work is data discs, ISO/BIN-CUE burning or disc copying on a known 64-bit PC, and you prefer a native build on principle. There is no features penalty for those jobs.
  • Choose portable over installer — in either bitness — if you want no installation and easy removal. See InfraRecorder Portable for sizes, hashes and USB use.
  • When a burn fails on x64 audio, retry the same project with the 32-bit build before you blame the disc or the drive. Swapping builds is a two-minute test that isolates the codec variable.

What bitness does not change

Bitness does not change Windows support. Neither build is officially supported on Windows 10 or 11; both generally run there, and both are subject to the blank-disc and verification reports discussed in our Windows 11 guide and Windows 10 guide. It does not change the licence, the price (free), the final-version status, or the need to verify every burn by reading the disc back. And it certainly does not add Blu-ray burning — for that, see the alternatives hub.

The short answer, then: default to 32-bit for audio and for maximum compatibility, use 64-bit for data work if you prefer native, and never let the label on the installer substitute for a read-back test. That test, not the architecture, is what tells you whether your disc is good.

A ten-minute test if you are still undecided

If you cannot decide from the codec explanation alone, let your own files decide. Build the same small audio project twice — once in the 32-bit portable and once in the 64-bit portable — using the tracks that actually caused you to ask the question, and burn each version to a rewritable disc if your drive supports it. Add every track without errors, note any file that one build accepts and the other questions, and read both finished discs back. In most households the result is clear within ten minutes: data-only users see no difference at all, while audio users with mixed libraries usually find the 32-bit build the calmer tool. Keep the winning folder, delete the other, and write down which build made any disc you archive, so a future problem can be traced to the build, the media or the drive rather than guessed at.

One final detail is worth recording in that note: the exact file you downloaded. The 32-bit installer is ir053.exe at 4,151,536 bytes and the 64-bit installer is ir053_x64.msi at 4,153,344 bytes — close in size, different in architecture and in the codec bundle described above. Naming the build, the file and the date in your burn log sounds fussy until the day a disc fails and that log is the only thing separating a codec issue from a dying drive.

Similar Posts