What Are Browsers?

Browsers are software applications that retrieve, interpret, and display content from the World Wide Web and local file systems, providing users with a graphical interface for navigating hyperlinked documents and interactive web applications. A browser takes a Uniform Resource Identifier (URI) as input, issues HTTP or HTTPS requests to the appropriate server, receives the returned resources, and renders them into a visual or auditory presentation. From Tim Berners-Lee's original WorldWideWeb application in 1990 through the graphically accessible Mosaic browser released in 1993 and the contemporary engines that dominate today's web, browsers have grown from simple document viewers into complex, multi-process runtime environments.

Modern browsers are built from several coordinated subsystems. The user interface layer handles the address bar, navigation controls, and bookmarks. A browser engine mediates between the user interface and the rendering engine. The networking layer manages HTTP connections, caching, and resource prioritization. A JavaScript engine executes scripts. A data storage layer manages cookies, session tokens, and local storage. Together these components must balance performance, security, and compatibility across an enormous diversity of content.

Rendering Engine

The rendering engine is responsible for converting HTML, CSS, and other resources into the visual page a user sees. As described in detail by Google's web.dev guide to how browsers work, the engine parses the incoming HTML into a Document Object Model (DOM) tree and parses stylesheets into a parallel CSS Object Model (CSSOM) tree. A render tree is then constructed by combining the two, and a layout pass assigns geometric coordinates to every element. A final paint operation draws pixels to the screen.

Three rendering engines dominate the contemporary browser landscape. Blink, originally a fork of WebKit, powers Chromium-based browsers including Chrome, Edge, Opera, and Brave, accounting for roughly 80 percent of desktop browser usage. WebKit remains the engine behind Safari on Apple platforms. Gecko powers Firefox. Each engine implements the HTML5, CSS, and ECMAScript specifications maintained by the W3C and the WHATWG, but differences in rendering speed, conformance, and privacy features continue to drive competition between them.

JavaScript Engine

JavaScript engines parse, compile, and execute the ECMAScript programs that implement interactive behavior in web pages and single-page applications. Contemporary engines do not interpret JavaScript line by line; they apply just-in-time (JIT) compilation techniques to translate frequently executed code paths into native machine instructions. V8, developed by Google and used in Chromium, introduced tiered JIT compilation and has been replicated in architecture by SpiderMonkey (Mozilla) and JavaScriptCore (Apple). The performance gains from JIT compilation, combined with the WHATWG Fetch API and the Web Workers API, have enabled browsers to run complex data visualization, gaming, and machine-learning workloads in a sandboxed environment without native installation.

Networking and Security

The networking subsystem resolves domain names, manages TLS handshakes, and enforces origin-based security policies. HTTPS adoption, driven by browser vendors beginning around 2015 through features such as the HTTP Strict Transport Security header and browser UI warnings for unencrypted pages, has made TLS the baseline expectation for public web content. The W3C web platform specifications define the Same-Origin Policy, Content Security Policy, and the mechanisms through which cross-origin resource sharing (CORS) can be selectively permitted. Browsers also implement sandboxing at the process level, isolating individual tabs and frames to limit the blast radius of a compromised renderer, following the architecture described in Google's site isolation security model. The IETF HTTP working group RFC for HTTP/2 and its successor HTTP/3 define the wire protocol improvements that reduce latency for multi-resource page loads.

Applications

Browsers have applications in a wide range of technology domains, including:

• Web application delivery and single-page application runtime environments
• Enterprise software access through browser-based thin clients
• Progressive web applications on mobile platforms
• Real-time communication via WebRTC for video conferencing and peer-to-peer data transfer
• Data visualization and scientific computing in browser-based Jupyter-style notebooks