ECMAScript
ECMAScript is the standardized scripting language specification that defines the core language behind JavaScript.
It is the language standard maintained through the ECMA-262 specification, while JavaScript is the most common implementation and ecosystem built on top of that standard.
What it does
ECMAScript defines how the language itself behaves.
It is commonly used to:
- Standardize JavaScript language features
- Define syntax, semantics, and core behavior
- Provide a stable spec for engines and runtimes
- Guide language evolution across yearly editions
- Keep implementations aligned across platforms
Core concepts
Language standard behind JavaScript
ECMAScript is the specification.
JavaScript is the most familiar real-world implementation and ecosystem built from that standard.
Specification, not framework
ECMAScript is not a library, browser API, or framework.
It defines the language rules that engines implement.
Edition-based evolution
ECMAScript evolves through published editions and accepted proposals.
That is why features are often discussed in terms of language standards and yearly updates.
Common use cases
- Explaining JavaScript language features
- Referring to the official standard
- Discussing language version support
- Understanding cross-engine behavior
- Distinguishing standard language features from browser or runtime APIs
Practical notes
- In everyday use, most people say JavaScript instead of ECMAScript.
- ECMAScript matters most when precision about the language standard is important.
- The standard and the surrounding ecosystem are related, but not identical.
- This page belongs near language fundamentals and implementation/runtime discussions.
Sources Used
- https://ecma-international.org/publications-and-standards/standards/ecma-262/
- https://tc39.es/ecma262/
Frequently Asked Questions
Is ECMAScript the same as JavaScript?
Not exactly. ECMAScript is the standard, while JavaScript is the most common implementation and ecosystem around it.
Why do people say ES6 or ECMAScript 2025?
Because ECMAScript evolves through published editions, and language features are often grouped by those editions.
Is ECMAScript a browser feature?
No. It is the language specification itself, not a browser-specific API.