Recommended Posts

As a longtime user of Firefox, I couldn't pass up the opportunity to use a 64-bit version of it. I figured I'd give it a try and it's something I've been thinking of doing since I first used Windows Vista Ultimate x64. I honestly never heard of Waterfox until I read this article on Neowin. I installed it on my main PC (Windows 7 Ultimate x64) and I really like it. It definitely feels speedier than the standard 32-bit version of Firefox and things like Flash also feel faster. Another positive thing is that YouTube videos no longer crash my display driver. I assume that using a 64-bit version of Flash had something to do with it.

Anyway, if you have a 64-bit operating system and are open to the idea of using a 64-bit browser than Waterfox is for you. You can download it here alongside its prerequisites.

FAQ:

What is Waterfox?

Waterfox is a high performance browser based on the Mozilla Firefox source code. Made specifically for 64-Bit systems, Waterfox has one thing in mind: speed.

Why should I use a 64-Bit version of Firefox?

For some people with older systems, the 64-Bit version loads quicker and is much more responsive than the 32-Bit build. For people with newer systems, it allows them to use the full potential of their systems.

If there are any bugs, where should I report them?

Unfortunately, since this is a 3rd party build you cannot report any bugs and you?ll just have to hope that they get fixed in the next update by Mozilla.

Is my experience limited if I use a 64-Bit version of Firefox?

The major plugins such as Adobe Flash, Sun Java, Microsoft Silverlight all have supported 64-Bit binaries available.

How does it compare to 32-Bit Firefox?

In benchmarks, the 64-Bit variant of Firefox out-performs the 32-Bit variant. Also because this variant is being built specifically for Windows, there might be further performance increases.

Were there any optimisations made?

Yes, Waterfox was compiled with SSE, SSE2, x64 favoring and the following optimisation flags: /Og /Oi /Ot /Oy /Ob2 /Gs /GF /Gy

Do all my Add-Ons work?

Yes! Add-Ons work on any version of Firefox, on any platform.

I get a msvcr100.dll is missing error.

You must have the Visual C++ Redistributable file linked in the download page installed.

How do I fix the blurry font?

Type about:config in the address bar. In the filter at the top type gfx.direct2d.disabled. Change it from false to true.

http://waterfoxproj....ceforge.net/faq

29l1hn6.png

Link to comment
https://www.neowin.net/forum/topic/1050079-waterfox-64-bit-version-of-firefox/
Share on other sites

I've always wondered just how they produce these 64bit builds, since for a long time the main codebase wasn't 64bit safe. Currently 64bit builds are still slower at JS than 32bit builds, and no amount of compiler optimisations will fix that.

Mozilla still don't consider the 64bit builds ready for anything but developer usage, they still crash randomly and often crash in such a way that the OS never calls their crash handling code (So the bugs go unreported)

I've always wondered just how they produce these 64bit builds, since for a long time the main codebase wasn't 64bit safe. Currently 64bit builds are still slower at JS than 32bit builds, and no amount of compiler optimisations will fix that.

Mozilla still don't consider the 64bit builds ready for anything but developer usage, they still crash randomly and often crash in such a way that the OS never calls their crash handling code (So the bugs go unreported)

I guess that was the case in the past. I haven't tried the 64-bit Nightly builds so I don't know how stable they are over the 32-bit Nightly builds. So far though, Waterfox hasn't crashed once. Perhaps Mozilla finally got around to making Firefox 64-bit friendly. Here's an interesting article about Firefox 8 (64-bit): http://www.extremetech.com/computing/90546-firefox-8-x64-has-64-bit-browsing-finally-come-of-age

I've always wondered just how they produce these 64bit builds, since for a long time the main codebase wasn't 64bit safe. Currently 64bit builds are still slower at JS than 32bit builds, and no amount of compiler optimisations will fix that.

Mozilla still don't consider the 64bit builds ready for anything but developer usage, they still crash randomly and often crash in such a way that the OS never calls their crash handling code (So the bugs go unreported)

I still think Mozilla needs to kill the current code and start from scratch.

Agreed, especially with Google having such a nice clean product as Chrome.

Considering it's withstood the competition quite well, I'm guessing a lot of people would disagree with you.

I'd prefer it if Firefox was optimized for SSE2 like Chrome is, but it's not really a concern if the performance is there. (The 64 bit version will be, of course, since all x64 procs have SSE2.)

Quite a lot of snakeoil and even a surprisingly outright lie, in fact. It is designed in hardware so that x86 code takes zero performance hit when run on an x64 machine. None, period.

As for optimization, setting compiler flags can do little magic if the code is not applicable for it. I would guess that forcing the matter can even make it slower as the dedicated instructions become efficient only when used properly.

As for compatibility improvements that are at least evident, I've, for one, settled for Nightly (and temporarily the latest Tracemonkey if it decides to crash).

I've had Waterfox, Palemoon and Aya... whatwasit for some time, run lenghty benches, too. Results were inconclusive but not something to make an impression that either was better than the other. It is no question that both Chrome and Oprah is faster in most cases. Even IE9 holds up in certain test cases.

All in all, if it works for you, good. If it doesn't, however, better be sure that those loud promises of these custom compiles being the fastest and whatnot are full of very big holes.

It's disappointing to me that the Firefox devs are still waffling over how to do it properly.

Like, we know what we need to do this, and we are making plans to do it, but we don't actually want to do it.

Heh.

They're working on it (see here). Unfortunately, it isn't a high-priority feature.

I guess that was the case in the past. I haven't tried the 64-bit Nightly builds so I don't know how stable they are over the 32-bit Nightly builds. So far though, Waterfox hasn't crashed once. Perhaps Mozilla finally got around to making Firefox 64-bit friendly. Here's an interesting article about Firefox 8 (64-bit): http://www.extremetech.com/computing/90546-firefox-8-x64-has-64-bit-browsing-finally-come-of-age

Even up to the mid point of 2011 they still had random chunks of code that assumed 32bit OSs (Converting pointers to 32bit integer, etc.). As for the article, that's entirely made up, what I think happened is that somebody noticed Mozilla was running 64bit regression tests, and assumed that meant an official release was coming (Which it isn't for a while until they sort all the problems out)

I still think Mozilla needs to kill the current code and start from scratch.

There's no reason to do that, the incremental upgrades they're doing now are much better (Stopping the project for a year to rewrite vs. rewriting a component incrementally over a couple of releases)

...

I'd prefer it if Firefox was optimized for SSE2 like Chrome is, but it's not really a concern if the performance is there. (The 64 bit version will be, of course, since all x64 procs have SSE2.)

It already is.

Have been using waterfox for the last few weeks so far and absolutely no problems whatsoever (same with firefox), constantly kept open for about 10 hours a day and memory usage always around 450MB (high res image threads, about 1GB then).

It is a wee bit more snappier and smooth than firefox 10 I find.

I guess that was the case in the past. I haven't tried the 64-bit Nightly builds so I don't know how stable they are over the 32-bit Nightly builds. So far though, Waterfox hasn't crashed once. Perhaps Mozilla finally got around to making Firefox 64-bit friendly. Here's an interesting article about Firefox 8 (64-bit): http://www.extremete...lly-come-of-age

Been using x64 nightly for months now and has been as stable as the x32 builds sharing almost all the same bugs. No reason not to use it especially now that flash has an x64 plugin.

Well, you say that, but it doesn't explain the devs discussing it as if it isn't used much over here http://groups.google...=64-bit&lnk=ol

The only discussion I can see is about having less code paths (Firefox includes SSE optimised code paths and normal paths, a native 64bit build doesn't need the normal code paths since it can guarantee the CPU can do SSE). And as a side effect it also means the compiler can include SSE functions anywhere, not just in optimised areas (As is done currently due to how compilers work)

Edit: So the question is "Can we use SSE everywhere?" not "Can we use SSE?"

Been using Waterfox for a while now. Even if it's built by Mozilla, it's NOT Firefox, so it has to be better!! Have NEVER liked Firefox.

Can't say as I've never noticed it being any faster than any other browser. All browsers runs blazingly fast on my sytems and the day that some one says about how slow a browser is on their systems, is the day I should go over and fix their computer!

Palemoon, http://www.palemoon.org/ also has a 64bit version, but I use the 32bit version of that on my 32bit machines.

As far as Chrome, if I were to ever use that again, which isn't happening, it would be SRWare Iron, NOT Google Chrome crap!!

What about the Windows Media Player plug-in?

Unfortunately, 32-bit plugins won't work with Waterfox. It's up to Microsoft to release a 64-bit version of the WMP plugin. So far though, the major plugins work: Flash, Java, and Silverlight.

Unfortunately, 32-bit plugins won't work with Waterfox. It's up to Microsoft to release a 64-bit version of the WMP plugin. So far though, the major plugins work: Flash, Java, and Silverlight.

And even the 32-bit plugin hasn't been updated for years, what's up with that!?

The only discussion I can see is about having less code paths (Firefox includes SSE optimised code paths and normal paths, a native 64bit build doesn't need the normal code paths since it can guarantee the CPU can do SSE). And as a side effect it also means the compiler can include SSE functions anywhere, not just in optimised areas (As is done currently due to how compilers work)

Edit: So the question is "Can we use SSE everywhere?" not "Can we use SSE?"

In 32bit code, since we have to explicitly think and do work about every place where we want to do SSE2, and since it's a performance/size compromise, we end up not doing it in many places.

So yes, I know they use it to some degree, but from what I can tell not much.

Been using Waterfox for a while now. Even if it's built by Mozilla, it's NOT Firefox, so it has to be better!! Have NEVER liked Firefox.

Can't say as I've never noticed it being any faster than any other browser. All browsers runs blazingly fast on my sytems and the day that some one says about how slow a browser is on their systems, is the day I should go over and fix their computer!

Palemoon, http://www.palemoon.org/ also has a 64bit version, but I use the 32bit version of that on my 32bit machines.

As far as Chrome, if I were to ever use that again, which isn't happening, it would be SRWare Iron, NOT Google Chrome crap!!

It's based on the Firefox source code so aside from being 64-bit, it's virtually identical to the official 32-bit version.

And even the 32-bit plugin hasn't been updated for years, what's up with that!?

That's one of the issues of using a 64-bit browser. If you use Firefox with a lot of plugins, then Waterfox may not be good. Fortunately, I only use a handful of plugins and most of them have 64-bit versions.

This topic is now closed to further replies.
  • Posts

    • All these CEOs got the biggest boners thinking about firing employees for AI. Turned out it was just a wet dream.
    • And the fact that the majority of people from Poland are white European Christians while the people you are complaining about in post after post are not is just a coincidence... Every sentence in your post I am replying to is racist nonsense. None of it is actually based on any facts whatsoever. All immigrants are seeking a better life too. It's literally the only reason they would risk everything and leave their homes, families, and homeland. They are working and contributing to the economy too, as you even admit. They get the same benefits your partner did AND that YOU are eligible for as well. That is one of the key things of the EU and a mark of a civilization. That is the definition of a society where everyone is given a chance, treated equally and fairly, and is judged by the content of their character, not their different skin color or which version of ignorant superstitious nonsense their parents lied about as children. Racists around the world said the same things about the Irish and Jews and Poles (like your partner) and...every other immigrant movement over the centuries. What's your family's heritage, by the way? Were your ancestors lied about with racist fearmongering crapola by self-entitled locals the same way as you are now? If someone like that said the same things about all people from Poland, like your partner, would they be right? Or would you want them to judge your partner based on who they actually were, not where they just happened to come from?
    • Again, this is an irrelevant attempt to attack the messenger. The truth does not require any justification.
    • Removed the blue and underline as you did not post a link. This would also  be considered spamming.
    • Why it's almost impossible to produce a smartphone in the United States by Hamid Ganji If you look at the back of some Apple products, you can see the famous phrase “Designed by Apple in California, Assembled in China.” This phrase appears on products from one of the largest smartphone brands in the United States. These products are designed in the U.S., but their manufacturing takes place in China, India, Vietnam, or even Brazil. But why can’t Apple, as one of the largest American tech companies, produce its iPhones on U.S. soil? The idea for this topic came to me after the Trump Foundation launched a smartphone called the T1 and claimed that it was designed and built with American values in mind. However, this claim did not last long, as it was revealed that Trump’s phone was actually a rebranded HTC U24 Pro, with only a gold case and minor internal component changes. You see? Even a phone that is supposed to represent American values is manufactured in China. With a gross domestic product (GDP) exceeding $32 trillion, the United States is currently the world’s largest economy, while China ranks second with around $20 trillion. On the other hand, the United States is by a wide margin the global leader in various technological fields, and American companies spend hundreds of billions of dollars annually on research and development. From Apple and Google to Microsoft, Lockheed Martin, Boeing, and others, American tech and industrial giants lead their foreign competitors in many sectors. The United States also has no shortage of smartphone brands. Apple, Google, and Motorola are among the major brands in the smartphone market, collectively holding a significant share. However, the vast majority of their products are manufactured outside the United States. So why is it that the world’s largest economy, home to the most advanced technology companies and industrial powers, cannot produce a smartphone on its own soil? Let’s explore this question together. Even threats to impose tariffs won’t work After Trump entered the White House as the 47th President of the United States, his administration adopted strict tariff policies. One of these policies was the imposition of a 25% tariff on smartphones manufactured outside the United States. Trump said he “had a little problem” with Apple CEO Tim Cook over producing smartphones outside the U.S. So he thought that threatening a 25% tax on imported phones might force Apple to bring manufacturing back to the United States. “I have long ago informed Tim Cook of Apple that I expect their iPhones that will be sold in the United States of America will be manufactured and built in the United States, not India, or anyplace else,” Trump wrote on Truth Social. Image via The White House Although Apple currently manufactures some of the iPhone’s chips in the United States with TSMC's help, it still shows no willingness to shift full iPhone production to the country. At the time, renowned Apple supply chain analyst Ming-Chi Kuo wrote on X, “In terms of profitability, it’s way better for Apple to take the hit of a 25% tariff on iPhones sold in the US market than to move iPhone assembly lines back to the US.” However, manufacturing a smartphone in the United States is not as easy as it might seem, and many technical and economic barriers are involved. The lack of necessary manufacturing hubs There is a clear reason why many companies prefer to manufacture their products in China. China has established itself as the main global manufacturing hub for international companies, and over the past few decades, large contract manufacturers have emerged there, allowing companies like Apple to outsource production. One such example is Foxconn, which also manufactures some Apple products in India. Building the infrastructure required to produce smartphones in the United States would require tens of billions of dollars in new investment. Factories would need to be built, essential manufacturing equipment would have to be installed, and, most importantly, a skilled workforce capable of operating these systems would need to be recruited and trained. The United States currently lacks the core infrastructure needed to manufacture smartphones, and for this reason, many companies prefer to outsource production to Chinese contractors rather than spend tens of billions of dollars to build that infrastructure, which is significantly more economically efficient. Additionally, building such infrastructure in the United States could take up to a decade, ultimately leading to a significant increase in the product's final price for consumers. Shortage of trained labor in the U.S. compared to China Decades of serving as a global manufacturing hub have allowed China to build a massive talent pool in the production sector that is almost unmatched worldwide. Today, if a company chooses to manufacture its products in China, it can be confident that the workers involved in production have years of experience in their respective roles and are capable of producing high-quality goods with minimal errors. Even if we assume that tens of billions of dollars were invested in building smartphone manufacturing infrastructure in the United States, finding skilled workers would remain highly challenging. Apple CEO Tim Cook visiting the iPhone 6 assembly line in China in 2014. Image: Tim Cook on X In a 2015 interview on CBS’s 60 Minutes, Tim Cook said the main reason Apple isn’t producing in the US is a lack of skills. "China put an enormous focus on manufacturing, in what you and I would call vocational kind of skills. The US over time began to stop having as many vocational kinds of skills. I mean you could take every tool and die maker in the United States and probably put them in the room that we're currently sitting in. In China you would have to have multiple football fields,” Cook said. Also, in 2017, at the Fortune Global Forum in Guangzhou, Cook once again emphasized the importance of highly skilled Chinese workers. “China has moved into very advanced manufacturing, so you find in China the intersection of craftsman kind of skill, and sophisticated robotics and the computer science world. That intersection, which is very rare to find anywhere, that kind of skill, is very important to our business because of the precision and quality level that we like. The thing that most people focus on if they’re a foreigner coming to China is the size of the market, and obviously, it’s the biggest market in the world in so many areas. But for us, the number one attraction is the quality of the people,” Apple CEO said. Higher labor costs in the United States Producing almost any product in the United States is more expensive than in many other countries, and one of the main reasons is the higher cost of labor in the U.S. According to the Bureau of Labor Statistics, median weekly earnings of full-time workers in the United States were $1,235 in the first quarter of 2026. Meanwhile, the average annual salary in China's private sector in 2025 was RMB 71,590 (US$9,961). In many parts of the world, the weekly wage of an American worker is equivalent to several months of income. Another important factor to consider is that in the United States, the workforce capable of working on a smartphone assembly line is highly specialized and therefore commands higher-than-average wages. According to an estimate by Bank of America, producing an iPhone in the U.S. is technically possible, but “iPhone cost can increase 25% purely on higher labor cost in the U.S.” However, this 25% increase applies only if final assembly is performed in the United States while components are still sourced from China or elsewhere. In this case, the price of a base iPhone would rise from $799 to around $1,000. But in another scenario, if Apple were to produce the required components for the iPhone within the United States, production costs could increase by more than 90%. Trump’s dream for a “Made in the USA” iPhone might never come true In a free-market capitalist economy, one of the primary responsibilities of any CEO is to maximize profit. Using Apple as an example, Tim Cook’s role is to maximize the company’s profits so that it can fund research and development for new products and invest in areas such as artificial intelligence, while also keeping shareholders satisfied. Therefore, it is entirely understandable that Apple would choose not to bring its manufacturing back to the United States and instead keep production in countries where labor is cheaper, and products can be manufactured at a lower cost, thereby maximizing its profit margins. What is your opinion about manufacturing smartphones in the United States? If you are an American citizen, would you be willing to pay hundreds of dollars more for a smartphone made domestically in the USA? Let us know in the comments.
  • Recent Achievements

    • Conversation Starter
      jessse3334 earned a badge
      Conversation Starter
    • Reacting Well
      JuvenileDelinquent earned a badge
      Reacting Well
    • One Month Later
      Excellence2025 earned a badge
      One Month Later
    • Week One Done
      Excellence2025 earned a badge
      Week One Done
    • Week One Done
      flexorcist earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      506
    2. 2
      +Edouard
      196
    3. 3
      PsYcHoKiLLa
      153
    4. 4
      Steven P.
      72
    5. 5
      FloatingFatMan
      65
  • Tell a friend

    Love Neowin? Tell a friend!