Format Factory Old Versions: 32-bit & Legacy Downloads
The current build is 64-bit only, which leaves a real, legitimate reason to look for an older release — here's what that older line actually is, and what to check before downgrading.
Why the current version dropped 32-bit support
Version 5.0.0, released in February 2020, moved Format Factory to a 64-bit-only architecture — every release since, up through the current 5.22.0.0, has continued that policy. This mirrors a broader industry shift: 64-bit Windows has been the default on new PCs for well over a decade, and dropping 32-bit support let the developer simplify testing and take advantage of newer encoding libraries more easily than maintaining both architectures in parallel.
The legacy v4.10.5.0 release
The last release built for 32-bit Windows is v4.10.5.0, which the developer distributes separately from the current 64-bit-only installer rather than through the same download page. If you need it specifically, check the developer's site directly for their archived-version listing rather than downloading a "v4.10.5.0" file from a third-party mirror — legacy releases are exactly the kind of file that gets repackaged with unwanted extras on unofficial download sites.
Older 64-bit releases
Between v5.0.0 in 2020 and the current 5.22.0.0, the developer shipped many incremental 64-bit releases — our full changelog page covers the milestones that actually changed functionality, like the v5.8.1 Windows 11 compatibility fix and the FFmpeg 7.1 engine upgrade in v5.20.0. Unless you have a specific compatibility reason to stay on an older 64-bit build, there's little upside to seeking one out over the current release, which includes everything those older versions did plus additional fixes and features.
How to downgrade safely
Uninstall the current version first through Windows Settings before installing an older one, rather than installing over top of it — this avoids leftover files from the newer version causing unpredictable behavior. Only source the older installer from the developer's own domain, and treat any third-party site offering a specific old version number as a higher-risk download than the current release, since it's a less scrutinized, less commonly downloaded file.
Older versions miss newer fixes
An older release won't include the Windows 11 compatibility fix from v5.8.1, the FFmpeg 7.1 engine upgrade, or any security-relevant patches shipped since. If your only reason for wanting an old version is uncertainty about the current one, our download and safety pages are the better place to resolve that instead of downgrading.
More legacy version questions
Will an old version still receive updates?
No — legacy releases like v4.10.5.0 are frozen at whatever state they shipped in. If you need ongoing updates and security fixes, only the current 64-bit line receives them.
Can I run an old version alongside the current one?
We haven't tested installing both simultaneously, and wouldn't recommend it without more certainty about how they'd interact — installing one at a time is the safer, more predictable approach.
Why people still search for old versions
Beyond the 32-bit case, some searches for old versions come from a different place entirely — someone remembers a specific version's interface or behavior and wants that exact experience back, or is troubleshooting a problem they suspect started with a recent update. If a specific version's behavior is what you're after rather than a genuine compatibility need, it's worth first checking whether the same result is achievable through a setting in the current version, since new releases add configuration options far more often than they remove them.
What you'd lose by staying on an old version
Format conversion itself is largely stable across versions — an MP4 you convert on an old 64-bit release will look the same as one converted on the current build for basic cases. What changes release to release is primarily codec support (newer formats like AV1 or VVC/H.266 simply don't exist in older versions), hardware acceleration coverage for newer GPUs, and document tools like the recent Markdown and CAJ additions. If your use case is narrow and doesn't touch any of those newer additions, an older 64-bit release will likely serve you fine — just without ongoing security patches.
Most readers don't actually need an old version
We're covering this topic thoroughly because real searches bring people here, but in practice, the large majority of readers who think they need an old version actually just need to confirm their Windows architecture — once you know you're on 64-bit, which covers most PCs from the last decade, the current release is almost always the better choice over anything older.
Confirm your architecture first
Every path on this page starts with the same question: are you actually on 32-bit Windows? If yes, v4.10.5.0 from the developer's own site is the legitimate answer. If no — which covers the overwhelming majority of readers — the current 5.22.0.0 release on our download page is the right choice, with none of the tradeoffs an older build carries.
Check before you assume you need 32-bit
Most PCs bought in the last ten-plus years run 64-bit Windows even if the user never explicitly checked — it's worth the thirty seconds to confirm via Settings → System → About before assuming you're in the smaller group that genuinely needs the legacy release.
Current unless proven otherwise
Default to the current release unless you have a specific, confirmed reason not to — that's the safest general rule for any actively developed software, this one included.