# Here is what you need to know about JavaScript’s Number type

Why 0.1+0.2 IS NOT equal to 0.3 and 9007199254740992 IS equal to 9007199254740993

AngularInDepthis moving away from Medium. More recent articles are hosted on the new platforminDepth.dev. Thanks for being part of indepth movement!

Most statically typed languages like Java or C have different data types for numbers. For example, if you need to store an integer that is in the range [-128;127] you can use ‘byte’ in Java and ‘char’ in C, which both take up only 1 byte. If you need to store a larger integer, you can use ‘int’ or ‘long’ data types which take up 4 and 8 bytes respectively. There are also separate data types that you can use to store numbers with fractional part — ‘float’ which takes up 4 bytes and ‘double’ with 8 bytes. These are usually referred to as floating point format and we’ll see later where this name comes from.

But we don’t have such a variety of number types in JavaScript. According to the ECMAScript standard, there is only one type for numbers and it is the ‘double-precision 64-bit binary format IEEE 754 value’. This type is used to store both integers and fractions and is the equivalent of `double` data type in Java and C. Some new developers to JavaScript do not realize that and believe that if they use **1** it is stored in 64 bits as:

while in fact it’s stored as:

This misunderstanding may cause a great deal of confusion. Let’s for example, take this loop written in Java:

How long will it run? It’s not difficult to see that it will stop after the first iteration. On the second iteration the counter

will be increased to **i**

, **2**

will produce **1/2**

which will be truncated to **0.5**

since the counter **0**

is an integer and the condition **i****1/2 > 0**** **will evaluate to false.

Now what do you think will happen if we write the same loop in JavaScript:

As it turns out this loop will never stop because the result of

is not evaluated as integer, but as a floating point and that leads to very interesting behavior. Want to learn more? Read on.**1/i**

I work as a developer advocate atag-Grid. If you’re curious to learn about data grids or looking for the ultimate Angular/React/Vue data grid solution, give it a try with our guide “Get started in 5 minutes” guide. I’m happy to answer any questions you may have.And follow me to stay tuned!

Those that are unfamiliar with the way JavaScript works usually mention another unexpected behavior that is easy to explain once you understand the language. Adding

to **0.1**

produces **0.2**

, which means that **0.30000000000000004****0.1+0.2**** **is not equal to

. Questions related to this behavior pop up so often that stackoverflow people had to add special note:**0.3**

It’s interesting that this behavior is often attributed to JavaScript, while it’s pertaining to any language the uses floating point format for numbers. This means that if you use ‘float’ or ‘double’ data types in Java or C you’ll see the same result. Another interesting point is that the result of

is not **0.1+0.2**

as seen in a browser’s console, but is actually **0.30000000000000004**

.**0.3000000000000000444089209850062616169452667236328125**

In this article I’d like to explain how floating point numbers work and take a close look at the *for loop* and *0.1+0.2* examples alluded earlier.

It’s worth mentioning BigInt, a new numeric primitive in JavaScript that can represent integers with arbitrary precision. With

`s, you can safely store and operate on large integers even beyond the safe integer limit for`

BigInt`s. It was introduced in V8 this year and is supported in Chrome 67+ and Node v10.4.0+. You can read more about it here.`

Number

# Representing numbers in the scientific notation

Before we start talking about floating point and the IEEE754 standard, we need to first look into what it means to represent a number in the scientific notation. In the general form the number in scientific notation can be represented like this:

*Significand *shows the number of significant digits. It’s also often referred to as *Mantissa *or *Precision*. Zeros are not considered significant; they just hold a place. *Base *specifies the numeric system base, i.e. **10**** **for decimal system and

for binary. **2***Exponent* defines by how many places a radix point must be moved to the left or right to obtain an original number.

Any number can be represented in the scientific notation. For example, the number

in decimal and binary systems can be represented like this:**2**

An exponent of zero simply shows us that no additional operations should be done to obtain the original number. Let’s see another example — the number

. The significant numbers here are **0.00000022**`22`

, so let’s remove zeros:

The calculation above demonstrates why the exponent of the base is decreased if the radix point moved to the right. So, by performing multiplication we refined our original number to have only significand digits:

Since we used multiplication by

, we had to compensate it by division and this is where negative exponent of **8**

comes from. The same process, only this time the division is used to obtain significand digits, can be performed on the number **8**

:**22300000**

This time the radix point was moved to the left and hence the exponent increased. As you can see, the scientific notation is a way to work easily with very large or small numbers. Depending on the exponent, the *significand* may represent an integer or a number with fractional part. When converting to the original number a negative exponent requires shifting the radix point to the left. The positive exponent requires shifting to the right and usually denotes large integers.

It’s also important to understand what a normalized form of a number is. A number is normalized when it is written in scientific notation with one nonzero decimal digit before the radix point. So, if we take our original numbers and represent them in the normalized form they will have the following representations:

As you may have guessed that the binary numbers will always have

before the radix point. Having numbers represented in the normalized form enables easy comparison of numbers by order of magnitude.**1**

Scientific notation can be thought of as a floating point representation of a number. The term *floating point* refers to the fact that a number’s radix point can “float” — it can be put anywhere relative to the significant digits of the number. And as we’ve learnt, the original position is indicated by the exponent.

# Floating point according to the IEEE754

The IEEE Standard for Floating-Point Arithmetic (IEEE 754)** **defines many things related to floating point arithmetic, but for the purposes of our exploration we’re interested only in how numbers are stored, rounded and added. I’ve written a very detailed article explaining how to round binary numbers. Rounding is a frequent operation and occurs when a selected format doesn’t allow enough bits to store a number. It is an important topic so get a good grasp of its mechanics. Now, let’s take a look at how numbers are stored. All examples onward are going to be mostly for numbers in binary system.

## Understanding how numbers are stored

There are two formats defined by the standard that are used most often — single and double precision. They differ in the number of bits each takes up and consequently in the range of numbers each format can store. The approach to translating a number in scientific notation into IEEE754 form is the same for all formats, only the number of bits allocated for mantissa (significand digits) and the exponent differ.

IEEE754 floating point allocates bits to store a number sign, its mantissa (significant digits) and exponent. Here is the how it distributes those bits in the double-precision format (64 bit for each number) used by JavaScript’s Number type:

The sign bit gets 1 bit, exponent — 11 bits and 52 bits are allocated for mantissa (significand). Here is the table that shows the number of bits allocated for each format:

The exponent is stored in the offset binary format. I’ve written a detailed article explaining this format and it’s differences against two’s complement. Please take some time to understand this topic as I’ll be using it when translating numbers into floating point format.

## Examples of how integers are stored

To see the bits distribution scheme I outlined above let’s see how the integers

and **1**

are stored. Number **3**

is represented in all numeric systems as **1**

so no conversion is required. It can be represented in scientific form as:**1**

Here we have a mantissa of

and the exponent of **1**

. Using this information you may assume that the number is represented in floating point like this:**0**

Let’s see if it’s really the case. Unfortunately, there are no built-in functions in JavaScript that allow you to see the bits pattern of a stored number. But I’ve written a simple JavaScript function that allows taking a look at how numbers are stored regardless of the your computer’s endianess. Here it is:

So, using it you can see that the number

is stored like this:**1**

It’s completely different from the assumptions set above. We have no digits in mantissa and there are

’s in the exponent. Now let’s see why it is so. **1**

The first thing we need to understand is that every number is translated from the *normalized *scientific form. What is the advantage of this? If the first digit before the radix point is always

, then there is no need to store it which gives one extra bit for mantissa digits. When performing mathematical operations this first digit **1**

is prepended back by hardware. Since number **1**

has no digits after the radix point in the normalized form and the first digit before the radix point is not stored, we have nothing to put into mantissa and so it’s all zeros.**1**

Now, let’s see where

’s come from in the exponent. I mentioned earlier that exponent is stored as offset binary. If we calculate the offset:**1**

we can see that this is exactly what we have in the representation. So under offset binary the value stored there is really

. If it’s unclear how the offset gives us **0**

read my article on offset binary.**0**

Let’s use the information we’ve learnt above and try to represent the number

in the floating point form. In binary it is represented as **3**

.**11**** **If you don’t remember why, check out my very detailed article on decimal-binary conversion algorithms. And upon normalization the number

has this form (numbers in binary):**3**

After the radix point we have only one digit of

that will be stored in mantissa. As explained earlier the first digit before the radix point is not stored. Also, normalization also gave us the exponent of **1**

. Let’s calculate how it’s represented in offset binary and then we have all the information required:**1**

One thing to remember about mantissa is that digits are stored in the exact order they are placed in the scientific form — left to right from radix point. With that in mind, let’s put all numbers in the floating point representation:

If you use the function I showed above you’ll see that we came up with the correct representation.

# Why 0.1+0.2 is not 0.3

Now that we know how numbers are stored, let’s see what happens in this often-cited example. The quick explanation goes like this:

Only fractions with a denominator which is a power of two can be finitely represented in a binary form. Since denominators of 0.1 (1 / 10) and 0.2 (1 / 5) are not powers of two, these numbers can’t be finitely represented in a binary format. In order to store them as a IEEE-754 floating point they have to be rounded to the number of available bits for mantissa — 10 bits for half-precision, 23 bits for single-precision or 52 bits for double-precision. Depending on how many bits of precision are available, the floating-point approximations of 0.1 and 0.2 could be slightly less or greater than there corresponding decimal representations, but never equal. Because of that fact, you’re never going to have 0.1+0.2 == 0.3.

This explanation maybe sufficient for some developers, but the best way to see what is going on under the hood is perform all the calculations that the computer is doing yourself. That’s what I’m about to do now.

## Representing 0.1 and 0.2 in the floating point format

Let’s see the bits pattern for

in floating point form. The first thing we need to do is to convert **0.1**

to binary. This can be done using the algorithm of multiplication by **0.1**

. I explain its mechanics in my article on decimal-binary conversion algorithm. If we convert **2**

to binary we get an infinite fraction:**0.1**

The next step is to represent this number in the normalized scientific notation:

Since mantissa can only have 52 bits, we need to round our infinite number to 52 bits after the radix point.

Using the rounding rules defined by IEEE-754 standard and explained in my article on binary numbers rounding we need to round the number **up** to:

The last thing left is to calculate the exponent representation in offset binary:

And when put into floating point format representation the number

has the following bits pattern:**0.1**

I encourage you to calculate the floating representation of

on your own. You should end up with the following representations in the scientific notation and binary:**0.2**

## Calculating the result of 0.1 + 0.2

If we assemble the numbers back from their representation as floating point into scientific form, here is what we have:

To add numbers, they need to have equal exponents. The rule says that we need to adjust the number with the smaller exponent to that of the larger. So, let’s adjust the exponent of

of the first number to have the exponent **-4**

like the second number:**-3**

Now we can add the numbers:

Now, the result of the calculation is stored in a floating point format, so we need to normalize the result, round if necessary and calculate the exponent in offset binary.

The normalized number falls right in the middle between the rounding options, so we apply tie-breaking rule and round **up **to the even. This gives the following resulting number in the normalized scientific form:

And when converted to the floating point format for storing, it has the following bits pattern:

**This is exactly the bits pattern that is stored when you execute the statement ****0.1+0.2****. **To get it, the computer has to round three times — one for each number and third time for their sum. When simply 0.3 is stored, the computer performs rounding only once.** This rounding operations lead to different bits pattern stored for ****0.1+0.2**** and for standalone ****0.3****. **When JavaScript executes comparison statement

, its these bits pattern that are compared, and since they are different the returned result is **0.1+0.2 === 0.3***false*. **If such formats existed than even with rounding the bits pattern would be equal, the ****0.1+0.2 === 0.3**** would evaluate to ****true**** regardless of the fact that ****0.1**** and ****0.2**** are not finitely representable in binary.**

Try checking the bits for the number

using the function I showed above **0.3***to64bitFloat(0.3).* The pattern will be different than the one we calculated above for the result of `0.1+0.2`

.

If you want to know what decimal number the stored bits represent, assemble the bits into the scientific form with zero exponent and convert them into decimal numeric system. The actual decimal number stored for

is **0.1+0.2****0.3000000000000000444089209850062616169452667236328125 **

and for

it is **0.3****0.299999999999999988897769753748434595763683319091796875.**

# Why the `for` loop never stops

The key to understanding why the *for* loop never stops is the number

. Let’s see what is special about that number.**9007199254740991**

## Number.MAX_SAFE_INTEGER

If you type Number.MAX_SAFE_INTEGER into console, it outputs our key number

. What is so special about that number that it got its own constant? Here is what ECMAScript Language Specification has to say about it:**9007199254740991**

The value of Number.MAX_SAFE_INTEGER is the largest integer

nsuch that n andn + 1are both exactly representable as a Number value. The value of Number.MAX_SAFE_INTEGER is9007199254740991(2⁵³−1).

And MDN also adds some explanation:

Safe in the constant name refers to the ability to represent integers exactly and to correctly compare them. For example,

`Number.MAX_SAFE_INTEGER + 1 === Number.MAX_SAFE_INTEGER + 2`

will evaluate to true, which is mathematically incorrect.

The first thing to understand is that this is not the largest integer that can be represented. For example, the number

which is **9007199254740994**

can be safely represented. The maximum number that can be represented can be seen using the constant **MAX_SAFE_INTEGER + 3**

and it’s equal to **Number.MAX_VALUE**

. What may come to you as surprise is that there are some integers that can’t be represented between **1.7976931348623157e+308**

and **MAX_SAFE_INTEGER**

. In fact, there’s an integer that can’t be represented between **MAX_VALUE**

and **MAX_SAFE_INTEGER**

. This number is **MAX_SAFE_INTEGER+ 3**

. If you type it into console, you will see that it evaluates to **9007199254740993**

. So, instead of working with the original number, JavaScript transformed it into the number less than the original by 1.**9007199254740992**

To understand why that happens, let’s first look at the bits representation of

in the floating point:**9007199254740991 (MAX_SAFE_INTEGER)**

which when converted to scientific form has the following representation:

Now, to get the binary resulting number with zero exponent we just move the radix point 52 places to the right and get:

So, to store the

number we used all places in the mantissa with the exponent of 52. Since all places are used, to be able to store the next number the only option we have is to increase the exponent by **MAX_SAFE_INTEGER**

to **1**

. For the exponent of **53**

, we move the radix point **53**

places to the right. But since we have only **53**

digits in the mantissa, we append **52**

at the end. For the exponent of **0**

two zeros will be appended. For **54**

— three. And so on.**55**

What implications does it have? You might have guessed already yourself. **Since we’re going to have all numbers larger than ****MAX_SAFE_INTEGER**** end with ****0****, no odd integer larger than ****MAX_SAFE_INTEGER**** can be represented in 64 bit floating point. **To be able to store some of them, the mantissa should be allocated more than 52 bits. Let’s see this in action:

You can see that the numbers

, **9007199254740993**

can’t be represented in **9007199254740995**

floating point. As exponent increases, the range of numbers that can’t be stored starts increasing dramatically.**64 bit**

## The never ending loop

Let me bring up the example with `for` loop here again:

It never stops. I mentioned in the beginning that it happens because the the result of

is not evaluated as integer, but as a floating point. Now that you know how floating point works and what **1/i**

it’s easy to understand why it never stops.**Number.MAX_SAFE_INTEGER**

For the loop to stop, the counter `i`

would have to reach `Infinity`

, since `1/Infinity > 0`

evaluates to `false`

. Yet it never happens. In the previous paragraph I explained why some integers can’t be stored and that they are rounded to the nearest even. So in our example JavaScript keeps increasing the counter `i`

by `1`

until it reaches `9007199254740993`

, which is `MAX_SAFE_INTEGER+2`

. And this is the first integer that can’t be stored, thus it gets rounded to the nearest even integer `9007199254740992`

. So the loop is stuck at this number. The loop won’t be able to get over it and we’ve got an infinite loop here.

# A few words about NaN and Infiinity

To concluded this article I’ve decided to give a very brief explanation of `NaN`

and `Infinity`

. `NaN`

stands for `Not a Number`

and it is not the same as `Infinity`

, although both are typically handled as special cases in floating-point representations of real numbers as well as in floating-point operations. They are distinct by having an exponent of `1024`

`(11111111111)`

as opposed to the `Number.MAX_VALUE`

, which has the exponent of `1023`

`(111111111101)`

.

Since `NaN`

is represented as floating point you should not be surprised that when you run `typeof NaN`

in a browser you’ll get `"number"`

. And it has the exponent of all `1`

’s and one non-zero digit in the mantissa:

There is a list of mathematical operations that result in `NaN`

, like `0/0`

or `Math.sqrt(-4)`

. In JavaScript there are some functions that can return `NaN`

. For example, `parseInt`

can return `NaN`

when used with a string parameter `parseInt(“s”)`

. The interesting thing is that any comparison operation with `NaN`

returns `false`

. For example, all operations below return `false`

:

`NaN`

, and only `NaN`

, always compares unequal to itself. To check if a value is `NaN`

, JavaScript has `isNan()`

function.

Infinity is another special case in floating point designed to deal with overflows and some mathematical operations, like

. Infinity is represented with all **1/0**`1`

’s in exponent and all zeros in mantissa:

For positive `Infinity`

the sign bit is zero, for negative `Infinity`

it’s 1. The MDN article describes some operations that result in `Infinity`

. Unlike `NaN`

, `Infinity`

can safely be used in comparisons.