Symbol type

By specification, object property keys may be either of string type, or of symbol type. Not numbers, not booleans, only strings or symbols, these two types.

Till now we only saw strings. Now let’s see the advantages that symbols can give us.


“Symbol” value represents an unique identifier with a given name.

A value of this type can be created using Symbol(name):

// id is a symbol with the name "id"
let id = Symbol("id");

Symbols are guaranteed to be unique. Even if we create many symbols with the same name, they are different values.

For instance, here are two symbols with the same name – they are not equal:

let id1 = Symbol("id");
let id2 = Symbol("id");

alert(id1 == id2); // false

If you are familiar with Ruby or another language that also has some sort of “symbols” – please don’t be misguided. JavaScript symbols are different.

“Hidden” properties

Symbols allow to create “hidden” properties of an object, that no other part of code can occasionally access or overwrite.

For instance, if we want to store an “identifier” for the object user, we can create a symbol with the name id for it:

let user = { name: "John" };
let id = Symbol("id");

user[id] = "ID Value";
alert( user[id] ); // we can access the data using the symbol as the key

Now let’s imagine that another script wants to have his own “id” property inside user, for his own purposes. That may be another JavaScript library, so the scripts are completely unaware for each other.

No problem. It can create its own Symbol("id").

Their script:

// ...
let id = Symbol("id");

user[id] = "Their id value";

There will be no conflict, because symbols are always different, even if they have the same name.

Please note that if we used a string "id" instead of a symbol for the same purpose, then there would be a conflict:

let user = { name: "John" };

// our script uses "id" property = "ID Value";

// ...if later another script the uses "id" for its purposes... = "Their id value"
// boom! overwritten! it did not mean to harm the colleague, but did it!

Symbols in a literal

If we want to use a symbol in an object literal, we need square brackets.

Like this:

let id = Symbol("id");

let user = {
  name: "John",
  [id]: 123 // not just "id: 123"

That’s because we need the value from the variable id as the key, not the string “id”.

Symbols skipped by for…in

Symbolic properties do not participate in loop.

For instance:

let id = Symbol("id");
let user = {
  name: "John",
  age: 30,
  [id]: 123

for(let key in user) alert(key); // name, age (no symbols)

// the direct access by the symbol works
alert( "Direct: " + user[id] );

That’s a part of the general “hiding” concept. If another script or a library loops over our object, it won’t unexpectedly access a symbolic property.

In contrast, Object.assign copies both string and symbol properties:

let id = Symbol("id");
let user = {
  [id]: 123

let clone = Object.assign({}, user);

alert( clone[id] ); // 123

There’s no paradox here. That’s by design. The idea is that when we clone an object or merge objects, we usually want symbolic properties (like id) to be copied as well.

Property keys of other types are coerced to strings

We can only use strings or symbols as keys in objects. Other types are coerced to strings.

For instance:

let obj = {
  0: "test" // same as "0": "test"

// both alerts access the same property (the number 0 is converted to string "0")
alert( obj["0"] ); // test
alert( obj[0] ); // test (same property)

Global symbols

Normally, all symbols are different. But sometimes we want same-named symbols to be the same.

For instance, different parts of our application want to access symbol "id" meaning exactly the same property.

To achieve that, there exists a global symbol registry. We can create symbols in it and and access them later, and it guarantees that repeated accesses by the same name return exactly the same symbol.

To can create or read a symbol in the registry, use Symbol.for(name).

For instance:

// read from the global registry
let name = Symbol.for("name"); // if the symbol did not exist, it is created

// read it again
let nameAgain = Symbol.for("name");

// the same symbol
alert( name === nameAgain ); // true

Symbols inside the registry are called global symbols. If we want an application-wide symbol, accessible everywhere in the code – that’s what they are for.

That sounds like Ruby

In some programming languages, like Ruby, there’s a single symbol per name.

In JavaScript, as we can see, that’s right for global symbols.


For global symbols, not only Symbol.for(name) returns a symbol by name, but there’s a reverse call: Symbol.keyFor(sym), that does the reverse: returns a name by a global symbol.

For instance:

let sym = Symbol.for("name");
let sym2 = Symbol.for("id");

// get name from symbol
alert( Symbol.keyFor(sym) ); // name
alert( Symbol.keyFor(sym2) ); // id

The Symbol.keyFor internally uses the global symbol registry to look up the name for the symbol. So it doesn’t work for non-global symbols. If the symbol is not global, it won’t be able to find it and return undefined.

For instance:

alert( Symbol.keyFor(Symbol.for("name")) ); // name, global symbol

alert( Symbol.keyFor(Symbol("name2")) ); // undefined, non-global symbol

For non-global symbols, the name is only used for debugging purposes.

System symbols

There exist many “system” symbols that JavaScript uses internally, and we can use them to fine-tune various aspects of our objects.

They are listed in the specification in the Well-known symbols table:

  • Symbol.hasInstance
  • Symbol.isConcatSpreadable
  • Symbol.iterator
  • Symbol.toPrimitive
  • …and so on.

For instance, Symbol.toPrimitive allows to describe object to primitive conversion. We’ll see its use very soon.

Other symbols will also become familiar when we study the corresponding language features.


  • Symbol is a primitive type for unique identifiers.
  • Symbols are created with Symbol(name) call.
  • Symbols are useful if we want to create a field that only those who know the symbol can access.
  • Symbols don’t appear in loops.
  • Symbols created with Symbol(name) are always different, even if they have the same name. If we want same-named symbols to be equal, then we should use the global registry: Symbol.for(name) returns (creates if needed) a global symbol with the given name. Multiple calls return the same symbol.
  • There are system symbols used by JavaScript and accessible as Symbol.*. We can use them to alter some built-in behaviors.

Technically, symbols are not 100% hidden. There is a build-in method Object.getOwnPropertySymbols(obj) that allows to get all symbols. Also there is a method named Reflect.ownKeys(obj) that returns all keys of an object including symbolic ones. So they are not really hidden. But most libraries, built-in methods and syntax constructs adhere to a common agreement that they are. And the one who explicitly calls the aforementioned methods probably understands well what he’s doing.

Tutorial map


read this before commenting…
  • You're welcome to post additions, questions to the articles and answers to them.
  • To insert a few words of code, use the <code> tag, for several lines – use <pre>, for more than 10 lines – use a sandbox (plnkr, JSBin, codepen…)
  • If you can't understand something in the article – please elaborate.