Mozilla builds open-source software that helps people browse the web privately. Its products include Firefox, a desktop and mobile browser, plus privacy tools like Mozilla VPN (encrypts internet traffic), Firefox Relay (masks email addresses and phone numbers), and Mozilla Monitor (checks for personal data in breaches). These tools work by delivering a private, controlled online experience: browse securely, hide contact details, and monitor data exposure. Unlike many rivals that rely on ads, Mozilla funds its services through search partnerships, distribution deals, and subscriptions, and it emphasizes openness and user choice.
Work here?Claim your company
Industries
Company Size
1,001-5,000
Company Stage
Grant
Total Funding
$3.5M
Headquarters
San Francisco, CA
Founded
1998
See people who can refer or advise you
Help us improve and share your feedback! Did you find this helpful?
Total Funding
$3.5M
Above
Industry Average
Funded Over
3 Rounds
Firefox 160: desktop on-device SpeechRecognition in 40 languages, an early-version Mini Window; MDN says a WebTransport change needs code updates. Mozilla's Firefox 160, released November 10, 2026, supports on-device SpeechRecognition on desktop in 40 languages and adds an early-version Mini Window; MDN lists WebTransport changes. Verified pipeline | Sources: 7 | Publisher: signed | Contributor: signed | Hash: b6cfe5db9d | View Overview. Mozilla released Firefox 160 on November 10, 2026, according to its release notes and MDN's developer notes. The release adds a Mini Window feature that Mozilla calls an "early version" and a "Never allow" button for sites that repeatedly ask to handle mailto: links. For web developers, MDN lists on-device speech recognition through the Web Speech API on desktop, several WebTransport changes, and a new CSS alias. LWN.net, OMG! Ubuntu and heise online each reported the release, and their feature lists differ in places, as noted below. An earlier Herald article covered Firefox 159. Speech recognition. Mozilla's release notes say the SpeechRecognition interface of the Web Speech API is now supported, "providing on-device, real-time speech-to-text in 40 languages." MDN's developer notes give the scope: the feature is "now available on desktop," and "Recognition is not supported on Android, and neither is remote (cloud) recognition." The firefox.com release notes do not state the desktop-only scope. MDN's guide to the Web Speech API describes how pages ask for on-device processing. A page sets the processLocally property, which defaults to false, to true. The guide says on-device recognition requires a one-time language pack download for each language, after which it is available offline. If processLocally is true and the language pack is missing, start fails with a language-not-supported error, and pages can check for packs with SpeechRecognition.available and install them with SpeechRecognition.install. According to the guide, the on-device-speech-recognition Permissions-Policy, whose default allowlist is self, controls those two methods. The guide describes the API generally and is not specific to Firefox. heise online says users "must first download an AI model for recognition" and that recognition afterwards works without an internet connection, with the website receiving the recognized text. MDN's guide calls the download a language pack; neither source explains the difference in wording. As of November 13, 2026, MDN's SpeechRecognition reference page carries a "Limited availability" label and says the feature is not Baseline because it does not work in some of the most widely-used browsers. WebTransport and other platform changes. * WebTransport: the WebTransport constructor accepts a headers option that adds custom HTTP headers to the extended CONNECT request, and the server's response headers are available in WebTransport.responseHeaders. The constructor also supports a datagramsReadableType option; set to bytes, it makes the incoming datagram stream a readable byte stream. * A change MDN says needs code updates: WebTransport.exportKeyingMaterial now requires a context argument and takes a new outputLength argument; previously, MDN says, the method always returned 32 bytes. MDN says code that omits either argument will need to be updated. * Renamed buffering properties: incomingMaxBufferedDatagrams and outgoingMaxBufferedDatagrams are supported and replace the non-standard incomingHighWaterMark and outgoingHighWaterMark, which MDN says have been removed. * CSS: ::-webkit-input-placeholder is supported as an alias of ::placeholder, which Mozilla's release notes say is meant to improve compatibility with sites that use it. * Removal: the non-standard MozScrolledAreaChanged event is no longer dispatched to web pages; setting the layout.scrolled-area-changed.content.enabled preference to true restores it. * Extensions: runtime.PlatformInfo now returns arm64 rather than aarch64 for ARM64 platforms, which MDN says aligns Firefox with Chrome. MDN also lists five features that ship in Firefox 160 but are disabled by default (the count is the Herald's, from the page's headings): render blocking, lazy loading for video and audio, the Speculation-Rules header, CSSNumericValue arithmetic methods, and the Canvas 2D colorSpace option. MDN says the header is enabled by default in Nightly and the arithmetic methods are supported in Nightly. For the canvas option, MDN says pixel data is not yet converted between color spaces, so getImageData returns the same pixels whichever color space is requested. Browser features. The release notes describe Mini Window as moving "a tab or a selected part of a page into an always-on-top window while browsing" and ask for feedback on "this early version of the feature." LWN says it is "in early development," while OMG! Ubuntu says it "is in beta." OMG! Ubuntu describes opening it from the tab context menu or the toolbar, and heise online gives a dashboard section kept visible while working in other tabs as an example. The release notes also list a Picture-in-Picture playback speed setting from 0.25x to 2.0x that appears only when the player window is medium-sized or larger; a "Never allow" button for sites that repeatedly ask to handle mailto: and other links; playback of Matroska (MKV) files with FLAC, MP3 or PCM audio; and WebGL rendering through Apple's Metal API on macOS, which Mozilla says "can improve performance on some sites." Other entries cover dragging history entries to the tab strip, a "Paste and Search" menu label, MathML accessibility in saved PDFs and Organize Tabs in French for Smart Window, which the notes say is part of a progressive roll out. Fixes include a freeze of several seconds when signing in to intranet sites using NTLM or Kerberos authentication. The notes also list "Various security fixes"; this article does not assess them. Where the accounts differ. OMG! Ubuntu's list of other changes includes "US users can now access the Yahoo! Scout in the chatbot sidebar." The en-US and en-GB release notes and MDN's developer notes, as read on November 13, 2026, contain no mention of Yahoo or Scout, and neither does LWN's brief or heise online's article. The sources do not explain the difference, and the Herald could not confirm the item. What the sources do not say. None of the cited sources says when Mini Window will move beyond its early stage, or what a page that does not set processLocally experiences in Firefox 160, where MDN says remote recognition is not supported.
Firefox tests Journeys feature that organizes your browsing history. Firefox Nightly is testing Journeys, a new Smart Window feature that groups related browsing history into topic-based cards with shortcuts to resume previous tasks. Nov 11, 2026 Mozilla is testing Journeys in Firefox Nightly, introducing AI-powered browsing history groups that help users return to previous research and unfinished tasks. Image generated by ChatGPT. We may earn from vendors via affiliate links or sponsorships. This might affect product placement on our site, but not the content of our reviews. See our Terms of Use for details. Firefox is testing a new feature that automatically groups related browsing history into topics, making it easier to return to research, shopping, or other unfinished tasks without digging through dozens of tabs. Called Journeys, the feature has appeared in Firefox Nightly as part of Mozilla's AI-powered Smart Window experience. It organizes previously visited pages into cards with summaries and shortcuts for reopening related websites. Journeys remains experimental, with no confirmed release date for the stable version of Firefox. The feature's interface and controls were detailed in Windows Report's Nov. 10 testing. How Firefox Journeys works. Journeys appears in a section labeled "Jump back in" on the Smart Window start page. Instead of presenting browsing history as a chronological list of websites, Firefox groups related activity into topic-based cards. Each card includes: * A topic title: A description of the activity, such as researching a product or planning a trip. * Related tab count: The number of pages associated with that topic. * Activity summary: A brief description of the browsing session. * Resume button: A shortcut to revisit the topic and continue working. Selecting Resume opens a new Smart Window tab containing a summary of the previous browsing session and suggestions for further exploration. Firefox also displays related pages, including Google searches and YouTube videos. Users can reopen individual pages or select all of them. The feature includes additional controls through a three-dot menu. "Open tabs" restores the pages associated with a Journey, while "Snooze until tomorrow" temporarily hides the card. A "Show more" option reveals additional browsing activity. These controls could help users resume tasks that span multiple sessions, particularly when they cannot remember the exact website or search terms they used previously. How Journeys differs from regular Firefox history. Traditional browser history records visited pages, generally organized by date or searchable by website. Journeys adds a layer of organization by grouping related activity into recognizable topics. For example, someone comparing laptops across several retailers and review sites could return to that research through a single Journey rather than searching for each page individually. Mozilla previously described this capability in its Smart Window announcement, saying it wanted to help users resume unfinished tasks by connecting related tabs and browsing history. The Nightly implementation now provides a more detailed look at that interface. Mozilla's broader Smart Window experience already supports AI-assisted tab grouping, duplicate-tab management, and visual previews of browsing history. Firefox has been experimenting with ways to organize browsing activity beyond traditional tabs. Earlier this year, Mozilla introduced Split View in Nightly, allowing users to view two websites side by side, alongside experimental Tab Notes. Journeys extends that focus on multitasking to browsing history, helping users return to related pages after a session ends. Is Firefox Journeys available, and what about privacy? Journeys is currently being tested in Firefox Nightly, Mozilla's early development channel. Nightly features can change significantly before reaching the stable browser, and Mozilla has not announced when Journeys will become generally available. The broader Smart Window experience is available in beta to eligible desktop users in the US, Canada, and France, according to Mozilla's explanation of its browser modes. Smart Window is optional. Users can continue browsing through Firefox's traditional Classic and Private windows without enabling the AI experience. What browsing information can Smart Window access? Smart Window can use browsing history, selected tabs, and webpage content to provide contextual assistance when users permit access. Mozilla says its AI assistant can use this information to compare products, summarize pages, generate recommendations, and help users continue previous tasks. Smart Window also supports memories that personalize responses over time. Mozilla says those memories are stored locally on the user's device and can be deleted. Private Windows remain separate from the AI-powered browsing experience. Mozilla has not yet published a separate technical explanation detailing how Journeys generates topic groupings, how long those groupings remain available, or whether users can manually edit them. Those details will be important for users deciding how much browsing activity they want the feature to organize. How to control Firefox's AI features. Firefox provides an AI Controls section where users can manage individual AI features or block them entirely. To review the available options: * Open Firefox Settings. * Find AI Controls under General settings. * Review the available AI features. * Enable or block individual features according to your preferences. A single setting can block current and future AI features and related prompts. Users can also manage individual capabilities, including AI translations, PDF alt text, tab-group suggestions, link previews, and chatbot integration. Firefox users who prefer traditional search results can install DuckDuckGo's No AI extension, which makes AI-free search the default for address-bar queries. The extension is separate from Mozilla's Smart Window controls, allowing users to manage AI-powered search results independently of Firefox's built-in features. Should you try Firefox Journeys now? Firefox Nightly offers an opportunity to experiment with Journeys before its wider release. However, Nightly is intended for testing and can contain unfinished features or stability issues. Users who depend on Firefox for everyday work may prefer to wait until Journeys reaches the beta or stable release channels. AI-powered browsing tools are becoming increasingly common. Chrome, Edge, Brave, Comet, and Dia take different approaches to AI-assisted browsing, including webpage summaries, contextual assistance, and automated tasks. Journeys focuses on browsing history, combining topic-based organization with shortcuts for reopening related pages. Its usefulness will depend on how accurately Firefox groups previous activity and how much control users have over the resulting cards. Mozilla has not announced a stable release date, and the interface may change as testing continues. Also read: Our comparison of privacy browsers examines Firefox, Brave, Tor, and other options for reducing tracking and protecting browsing activity.
Firefox strengthens protection against browser fingerprinting. Mozilla has limited the information that helps websites recognize Firefox users without cookies. The new measures could affect analytics and visitor identification systems. Mozilla has strengthened Firefox's protection against browser fingerprinting. In a November 11, 2026 article, the company says the changes reduce the amount of information scripts can use to distinguish visitors across websites without cookies. Some measures are already enabled by default, while Mozilla is rolling out additional restrictions gradually. What information the browser now reveals differently. A browser fingerprint is made up of characteristics of the browser and device: available fonts, screen dimensions, graphics hardware, and other properties. Each may seem like an ordinary technical detail, but together they can help identify a browser as someone moves between websites. This kind of tracking does not require a cookie to be stored. Mozilla examined which characteristics do the most to set users apart. Its research showed that protecting a relatively small number of browser features can significantly weaken common fingerprinting methods. Rather than trying to hide every property, the company focused on differences whose removal has a measurable effect. For example, Firefox limits the data available through the screen resolution API, making it harder to determine the size and position of the system taskbar or dock. Instead of reporting the exact number of processors, the browser may report 4 or 8. This makes a device's configuration less useful for identification. Firefox still provides information websites need to function, including language and time zone. The browser also randomizes some other signals, but the benefit is harder to measure, so they were not included in this study's results. What Mozilla measured and when the restrictions apply. To assess the protections, researchers simulated the measurements collected by Fingerprint Pro, Signifyd, and Akamai scripts, then tested how well combinations of that data distinguish users. The study used measurements from nearly 25 million Firefox users. The results are described in a paper accepted for publication at the 2026 Computer and Communications Security (CCS) conference; Mozilla has also prepared a project page and a browser-based test. While collecting data, Mozilla used OHTTP to separate IP addresses from request contents: neither the intermediary nor the company received both parts together. Access to the telemetry and its retention period were limited. Individual records were deleted several months ago, leaving only aggregated results for publication. According to Mozilla, the measures studied made fingerprints less precise: fewer users had a unique combination of properties, and groups sharing the same fingerprint grew. The most recent changes evaluated were included in Firefox 145. The research also helped eliminate differences in image rendering, Web Audio, and mathematical operations on Android that had made browsers easier to tell apart. The protections are not all being introduced at once. Hiding information about the system taskbar, for example, is enabled by default in every mode. Mozilla is rolling out some other measures first in private browsing and with the Strict setting in Enhanced Tracking Protection. To apply the additional restrictions in all Firefox windows, you need to select Strict. If that setting interferes with a website, you can change it. The company has not said when the remaining measures will be enabled by default. What this means for websites and analytics. Website owners and marketers should distinguish between counting visits and trying to recognize visitors by their browser characteristics. If an analytics or identification system relies on that kind of fingerprint, its results for Firefox users may change: the combinations of properties studied are now less effective at telling one person from another. The published results cannot show how noticeable the effect will be for a particular website. Developers should check workflows that depend on exact screen resolution, processor count, or other measurable characteristics. Mozilla aims to keep websites working, but testing only in a regular window with default settings is not enough to see how the additional measures behave in private browsing or with Strict enabled. This does not mean fingerprinting is now impossible: Mozilla acknowledges that fingerprinting methods may change. Firefox has other protections, too, including Total Cookie Protection, which isolates cookie-based identifiers. But the study's conclusion is narrower: the measures examined make browsers less distinguishable by the selected characteristics. My take: test real-world workflows. I appreciate an approach that measures whether a protection works while also making sure websites keep working. For a designer, it is a familiar trade-off: reveal less data without breaking the task that brought someone to the page. An elegant privacy model is not much help if a form stops working under strict protection. I would test changes like these against real-world workflows, especially on mobile: it helps to account for their constraints from the start of a project. I would also discuss an interface's dependence on browser data with developers, rather than only at the mockup stage. Understanding HTML and CSS helps you spot earlier where a solution relies on a property being precise when the browser no longer guarantees it. Sources. Where the news comes from. The text is a retelling in the author's own words; the facts come from the source, the opinion is the author's.
Firefox 160 releases with new Mini floating Windows and UI improvements. Tuesday, November 10th 2026 Mozilla has officially released Firefox Browser version 160, which brings with it both a number of under-the-hood and user-facing changes to improve the average browsing experience. Aside from a few technical changes, like support for MKV playback with FLAC, MP3 or PCM audio, the biggest new user-facing changes are the new Mini Windows and an updated UI for the PiP (Picture-in-Picture) video player. Mini Windows is a new early implementation of a feature that allows users to move a tab or a part of a page into an always-on-top window. To access Mini Windows, you right-click a tab, and select "Move to Mini Window," and you can then right-click any section of page content and select "Move Section to Mini Window," which will bring up a new UI to select and isolate a particular section of a page for use in the mini window. On the PiP side, Mozilla has added a playback speed button and slider interface, so that users no longer need to navigate back to the tab to access playback speed. There are also a number of performance improvements and fixes, including: * Metal API rendering for WebGL content on macOS, resulting in performance improvements on some sites * Pages saved as PDFs make MathML content available to screen readers * Address bar UI and bug fixes * Bug fixes for background links opened by other apps in macOS
OpenAI releases GPT-6 Cyber. OpenAI has released another cybersecurity-focused AI model for security research, with the release of GPT-6 Cyber. Published: 11/05/2026 At a Glance * Release: OpenAI introduces GPT-6 Cyber for security research. * ExploitGym: Scores 48.5%, up from 32.1% for GPT-5.6 Cyber. * Scope: Avoided out-of-scope exploits in 99.93%-100% of tests. * Impact: 948 Linux privilege-escalation exploits; 81 novel Firefox vulns. * Access: Initially limited to approved Daybreak Red customers. OpenAI has released another cybersecurity-focused AI model for security research, with the release of GPT-6 Cyber. Few industries have been so completely upended as the cybersecurity industry. Security researchers and bad actors alike have been using AI to find vulnerabilities in operating systems, platforms, and applications at an unprecedented pace. The issue has become so pronounced that the leading AI companies are restricting access to their most powerful models, only giving access to trusted companies and researchers. OpenAI has now released another major model aimed at security research, which the company announced in a blog post: WebProNews, Inc. is introducing GPT-6 Cyber, a major leap in security research: more capable at finding and fixing vulnerabilities, and far more reliable staying within the boundaries researchers set. GPT-6 Cyber delivers major gains on key cybersecurity benchmarks over GPT-5.6 Cyber, including a 51% relative improvement on ExploitGym and a step function improvement when tested on staying within scope. It is already helping to secure real-world software, uncovering and validating thousands of exploits in security-critical codebases such as Linux and Firefox. The new model scores significantly better than GPT-5.6 in ExploitGym tests: On ExploitGym, which tests whether models can exploit a specified vulnerability, GPT-6 Cyber scores 48.5%, up from 32.1% for GPT-5.6 Cyber. It also follows task boundaries more reliably: in a separate alignment evaluation, GPT-6 Cyber avoided exploiting out-of-scope services in 99.93% of tests without its deployment prompt, and 100% with this prompt. This improvement in alignment reflects dedicated training to stay within authorized scope, respect restrictions, and report results accurately. The company outlined the success GPT-6 has already scored, while acknowledging the limited window available to secure software: These capabilities are already helping secure real systems. Its researchers used GPT-6 Cyber to develop 948 privilege escalation exploits in Linux and identify 81 previously unknown high-severity vulnerabilities in Firefox, despite extensive prior testing with frontier models. The model also helped develop candidate patches, and Mozilla has released fixes for many of the Firefox vulnerabilities(opens in a new window). Security teams at Cisco, Calif, and CodeRabbit are using it for vulnerability research and code review, and WebProNews, Inc. has relied on it to find and fix weaknesses in its own infrastructure. It is clear that WebProNews, Inc. has a limited window to use frontier models to secure software. Its goal is to dramatically expand Daybreak, bringing advanced security research to organizations of every size, independent researchers, and open-source maintainers. Mainline models such as GPT-6 Astra already support code review, vulnerability triage, and patch development. Daybreak Blue helps verified defenders validate vulnerabilities and fixes with fewer unnecessary refusals, while Daybreak Red enables deeper exploit development and authorized security testing with GPT-6 Cyber. As with other similar models from Anthropic and Google, GPT-6's access is limited to trusted partners: GPT-6 Cyber is initially available through the API and Codex to a select group of approved Daybreak Red customers. WebProNews, Inc. will progressively expand access to all Daybreak Red customers soon, and are also making GPT-5.6 Cyber available to all Daybreak Red customers. Subscribe for Updates A focused newsletter covering the security, risk, and governance challenges emerging from the rapid adoption of artificial intelligence.
Find jobs on Simplify and start your career today
Don't see your dream role? Check out thousands of other roles on Simplify.Browse all jobs
Industries
Company Size
1,001-5,000
Company Stage
Grant
Total Funding
$3.5M
Headquarters
San Francisco, CA
Founded
1998
Find jobs on Simplify and start your career today
Don't see your dream role? Check out thousands of other roles on Simplify.Browse all jobs