Definition:
Safari is a web browser developed by Apple and integrated into macOS, iOS, iPadOS, and visionOS. It uses WebKit to process and render web content, and connects with Apple ecosystem features such as iCloud, Keychain, Handoff, Apple Pay, and system privacy controls. Its capabilities vary according to the device, operating system version, and regional availability of each feature.
Table of contents
Origin, WebKit, and architecture
Apple introduced Safari in 2003 to replace Internet Explorer as the Mac’s default browser. Its engine originated from KHTML and KJS, open-source projects that led to WebKit. Safari and WebKit development are related, but they are not the same entity.
A web browser includes the interface, profiles, synchronization, permissions, and other user-facing services. WebKit is the open engine that interprets HTML and CSS, runs JavaScript through JavaScriptCore, and coordinates content, network, graphics, and storage processes. Safari uses this engine but adds Apple’s own features and policies.
The multi-process architecture separates the interface, web content, and certain services. This isolation helps contain failures and applies boundaries between websites, although it does not eliminate every vulnerability. Safari and WebKit updates arrive through system or browser updates, depending on the platform and version.
Safari is primarily available on Apple devices. The old Windows version stopped receiving maintenance years ago and should not be considered a current option. Other browsers may use WebKit on certain platforms without sharing Safari’s interface, synchronization, or policies.
Browsing, profiles, and integration
Safari can open tabs and groups, save bookmarks, display history, download files, use Reader mode, and translate supported pages. On compatible devices, it can also install certain websites as web applications, although their capabilities depend on the website and operating system implementation.
Integration with an Apple Account adds several related but distinct functions:
- iCloud can synchronize bookmarks, tabs, groups, history, and other authorized data;
- Keychain and the Passwords app can store and fill passwords and passkeys;
- Handoff allows a page to be continued on another nearby device linked to the same account;
- Apple Pay can be used on compatible websites without providing the merchant with the actual card number;
- Continuity controls can share links, reading lists, and other activities across devices.
Safari profiles separate history, cookies, website data, tab groups, favorites, and extensions for contexts such as work and personal use. They are not equivalent to creating a different system account. If synchronized through iCloud, a profile may appear on other devices linked to the same account.
Separating profiles does not prevent a website, network, or service from recognizing the same user through a sign-in or other signals. It also does not turn a profile into an isolated environment for handling sensitive information.
Apple Intelligence in Safari
On compatible devices, Safari can use Apple Intelligence to summarize the content of certain pages. The feature works through Reader mode or available page controls and generates a condensed version of text that the system can process. Writing Tools can also help summarize selected content.
Apple Intelligence in Safari requires compatible hardware, software, language, and settings. Availability may vary by region, and not every page supports Reader or a summary. Enabling Apple Intelligence on the device is different from signing in to a website.
A generated summary does not replace the original content. It may omit an exception, misinterpret a relationship, or reduce important information. The complete source should be consulted before making a decision based on legal, health, financial, or technical material.
Apple Intelligence is not Safari’s engine and does not control search result rankings by itself. It is an optional layer applied to certain tasks; WebKit continues to process the page, while the selected search engine handles queries entered in the address bar.
Privacy, permissions, and security
Safari includes Intelligent Tracking Prevention to limit certain forms of cross-site tracking. This system uses machine learning and rules concerning storage and third-party resources, but it does not block all data collection or make browsing anonymous.
Apple allows users to prevent cross-site tracking and manage cookies, stored data, and permissions. Blocking resources or limiting storage may affect sign-ins, embedded content, or features that depend on third parties. Privacy and compatibility may therefore require different decisions for each website.
Private browsing prevents Safari from retaining certain session details after private windows are closed and separates its tabs from ordinary use. It does not hide activity from the visited website, the internet provider, a managed network, or services where the user signs in.
Location, camera, microphone, notification, and download permissions are managed per website and through the operating system. Fraudulent website warnings, process isolation, and updates reduce known risks, but they do not guarantee that a page, download, or extension is safe.
Extensions, development, and limitations
Extensions can modify pages, block content, or connect Safari with other services. They are primarily distributed through the App Store and request permissions according to the pages and data they need. Availability in the store does not remove the need to review the developer, permissions, privacy policy, and updates.
Apple documents how to manage Safari extensions. Activation may vary by profile, and extensions with website access are usually disabled initially in private browsing. An incompatible, abandoned, or overly permissive extension can affect privacy, stability, and performance.
For web development, Safari includes Web Inspector and tools for examining documents, networking, storage, performance, and accessibility. WebKit releases progressively implement standards and APIs; the Safari 26 technical notes show that each update also includes fixes, changes, and deprecations.
A website should not be evaluated only in Safari or on one device. Differences between engines, screen sizes, permissions, and versions may produce different results. Testing should cover relevant browsers and platforms, especially when a function depends on recent APIs or operating system behavior.
Safari combines WebKit with Apple’s own services and controls. Its actual behavior depends on the version, hardware, account, permissions, extensions, and visited website. Integration, privacy, performance, and compatibility should be understood as characteristics conditioned by that context, not as absolute guarantees.