Zen is the best way to browse the web.
Beautifully designed, privacy-focused, and packed with features. +We care about your experience, not your data.
404
Page not found. Check the URL or try using the search bar.
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+Examples of behavior that contributes to a positive environment for our community include:
+Examples of unacceptable behavior include:
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+This Code of Conduct applies within all community spaces, and it also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [insert contact method]. All complaints will be reviewed and investigated promptly and fairly.
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community. +Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+Community Impact: A violation through a single incident or series of actions. +Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+Community Impact: A serious violation of community standards, including sustained inappropriate behavior. +Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals. +Consequence: A permanent ban from any sort of public interaction within the community.
+This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
+Community Impact Guidelines were inspired by Mozilla’s code of conduct enforcement ladder.
+For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
Thank you for considering contributing to Zen Browser! We appreciate your time and effort in improving this project. The following is a set of guidelines for contributing to Zen Browser. These guidelines are intended to make it easier for you to get involved.
+We welcome a wide range of contributions, including but not limited to:
+To help you get started with contributing, we have created separate guides for each repository:
+Please follow the appropriate guide based on the repository you want to contribute to.
+If you find a bug, please open an issue and describe the problem in detail. Include steps to reproduce the bug, the expected behavior, and any relevant information about your environment. Please verify that the bug has not been reported already.
+ +
We welcome suggestions for new features or improvements to existing ones. To suggest a feature, please start a new Github discussion in the Ideas category. +Use the correct Github Repository based on the list above
+Please note that this project is governed by a Code of Conduct. By participating in this project, you agree to abide by its terms.
+By contributing to Zen Browser, you agree that your contributions will be licensed under the MPL-2.0 License.
+Thank you for your interest in contributing to Zen Browser! We look forward to your contributions.
Contributing to the Zen Browser Desktop project is a great way to get involved with open-source software development. This guide will walk you through the steps to clone the project, set up your development environment, make contributions, and submit pull requests.
+Before you begin, ensure you have the following tools installed:
+We’ve took the time to make building Zen Browser as easy as possible, independent of your operating system or technical knowledge.
+ +First, you need to clone the Zen Browser repository to your local machine. This will create a local copy of the project that you can work on.
+git clone https://github.com/zen-browser/desktop.git --recurse-submodulescd desktop--recurse-submodules: This flag ensures that all submodules are cloned along with the main project. Zen Browser relies on several submodules, so this step is essential.Once you have cloned the project, navigate to the project directory and install the necessary dependencies using npm:
+npm iThis command will install all the packages listed in the package.json file, which are required for building and running Zen Browser.
To set up the browser, you need to download additional files and prepare the environment:
+npm run initThis command handles all the necessary bootstrapping tasks, such as setting up configuration files and downloading essential resources.
+Before building the browser, it’s recommended to update the American English language packs to ensure that all localization files are up-to-date:
+sh ./scripts/update-en-US-packs.shThis script updates the “en-US” localization files, which are necessary for proper language support in Zen Browser. Running this step ensures that your build includes the latest translations and language resources.
+Now that everything is set up, you can build the browser:
+npm run buildThis command compiles the source code and creates the necessary files for running Zen Browser.
+After building the browser, you can start it using:
+npm startThis command launches the browser, allowing you to see your changes in action.
+You can contribute to Zen Browser in various ways, including:
+Before contributing, please keep the following guidelines in mind:
+Fork the Repository: Create a fork of the Zen Browser repository on GitHub.
+Create a New Branch: It’s a good practice to create a new branch for each feature or bug fix.
+git checkout -b feature/your-feature-nameMake Your Changes: Edit the code in your local repository.
+Commit Your Changes: Commit your changes with a descriptive message.
+git commit -m "Add feature: your feature description"Push Your Changes: Push your branch to your forked repository.
+git push origin feature/your-feature-nameSubmit a Pull Request: Go to the original Zen Browser repository and submit a pull request from your forked repository.
+Thank you for contributing to Zen Browser! Your contributions are valuable and help make the project better for everyone.
Thank you for your interest in contributing to the translations for Zen Browser! Ensuring that Zen Browser is accessible to users around the world is a key priority, and your contributions help make this possible. This guide will walk you through the process of getting started with translating Zen Browser using Crowdin.
+ +Before you begin, you will need to have the following:
+Once you have joined the project and selected your language, you can start translating:
+In addition to translating, you can also review translations made by others:
+Crowdin provides communication tools to collaborate with other translators:
+Crowdin allows you to track the progress of the translation project and stay updated on new strings that need translation:
+Thank you for helping to make Zen Browser accessible to a global audience! Your contributions are invaluable.
This guide will walk you through the steps required to set up and contribute to the development of Zen Browser’s homepage. Whether you’re fixing bugs, adding new features, or enhancing the design, this guide will help you get started.
+Before you begin, make sure you have the following installed on your machine:
+Once you have forked the repository, clone it to your local machine using the following command:
+git clone https://github.com/<your-username>/www.gitcd wwwReplace <your-username> with your GitHub username.
Navigate to the project directory and install the required dependencies:
+npm installThis command installs all the necessary packages listed in the package.json file.
After installing the dependencies, you can start the development server:
+npm startThis command will start a local server and open the homepage in your default web browser. The server will automatically reload whenever you make changes to the code.
+You can now start making changes to the homepage. The project structure is as follows:
+Feel free to explore and modify the files to implement new features or fix bugs.
+Before submitting your changes, make sure they work as expected. Check the functionality across different pages and ensure that your changes do not introduce any new issues.
+Once you are satisfied with your changes, commit them to your local repository:
+git add .git commit -m "Description of your changes"Push your changes to your forked repository:
+git push origin mainAfter pushing your changes, go to the original Zen Browser Homepage Repository and submit a pull request:
+Your pull request will be reviewed by the maintainers, and you may be asked to make some adjustments. Once approved, your changes will be merged into the main branch.
+Thank you for contributing to Zen Browser’s homepage! Your contributions help make the project better for everyone.
This guide provides an overview of the differences between the generic and optimized builds of Zen, so you can make an informed decision on which version to use.
+ +The optimized version of Zen leverages Advanced Vector Extensions 2 (AVX2), a CPU instruction set that enhances performance for certain computational tasks. This instruction set is only available on modern processors.
This guide provides step-by-step instructions for installing Zen Browser on macOS, including how to bypass macOS Gatekeeper due to the lack of an official Developer License. It also explains how users can support the Zen Browser team by donating towards obtaining a Developer License.
+ +
Upon trying to open Zen Browser, you may encounter a message indicating the file is damaged. This happens because the app does not have a valid developer signature and is using an Ad-hoc sign.
+
Open Terminal.
+Run one of the following commands:
+xattr -c '/Applications/Zen Browser.app/'xattr -d com.apple.quarantine '/Applications/Zen Browser.app/'After running the command, if successful, Terminal will return a blank line.
+
At the time of writing, there seems to be a bug with Zen Browser where the menu might not display correctly on the initial start. To fix this, quit Zen Browser (⌘Q) and reopen it.
You should now have a fully functional Zen Browser on your macOS. If you need to uninstall Zen, you can use Pearcleaner.
+ +Thanks to SenpaiHunters for creating this guide
+Original Post: Issue #53
This guide will help you customize the appearance of Zen Browser by live editing the userChrome.css file. Follow the steps below to start customizing your browser’s theme.
about:support in the address bar and press Enter.chrome Folderchrome.chrome folder, create a new blank file named userChrome.css.Ctrl + Shift + Alt + I to open the Developer Tools.userChrome to locate the userChrome.css file you created earlier.userChrome.css FileuserChrome.css file should now be visible in the Style Editor.
+to hover over and select elements on the page. This allows you to learn about the id, class, or other attributes of elements, which you can then target in your userChrome.css file.Ctrl + S.This guide is designed to help you quickly and efficiently customize your Zen Browser experience. Happy theming!
This guide will give you a comprehensive understanding of Firefox profiles, helping you manage them effectively even in the most challenging situations. By following this guide, you’ll learn how to preserve key elements of your browsing experience, including bookmarks, history, passwords, and more.
+This guide will help you:
+about:config settingsabout:support in Firefox.After turning off Firefox, copy the following files from your profile folder:
+about:config settings.about:profiles in Firefox.about:support again and open the profile folder for the new profile.After ensuring everything works correctly, go back to about:profiles and set the newly created profile as the default. This will make it your main profile moving forward.
By following these steps, you’ll maintain a consistent and personalized browsing experience across different Firefox profiles.
This guide will hlep you creating a portable version of Zen Browser, it is straightforward. You just need to create a shortcut with the -P option for Zen Browser, and then you can open it normally, set it as the default browser, and pin it to the Taskbar.
Zen-Browser-Setup-xxx.exe.Zen-Browser-Setup.exe file.core folder inside the extracted files.core folder to any location of your choice.ZenBrowser (or any name you prefer).ZenBrowser folder you just created.CMD and press Enter to open the Command Prompt in this directory.zenbrowser.exe -P and press Enter. This will open the Profile Management window.zenbrowser.exe for portability.zenbrowser.exe with the -P option.This guide addresses a known issue where Zen Browser may crash randomly or repeatedly on Linux systems using Wayland. While this issue primarily affects Linux users, particularly on Wayland, it’s important to note that the problem is upstream and is expected to be fixed in Firefox 130. This guide also provides steps to work around the issue for users who installed Zen via different package managers or Flatpak.
+ +If you installed Zen Browser via a package manager (e.g., yay, paru, nix, etc.), you can try the following:
Use a menu editor (e.g., libre-menu-editor) to edit the Zen Browser menu file.
Add the following environment variable at the beginning of the command:
+MOZ_ENABLE_WAYLAND=0If you installed Zen Browser via Flatpak (e.g., GNOME Software, KDE Discover, flatpak command, etc.), there are a few options you can try:
+Apply the Environment Variable:
+Run the following command to set the environment variable, but be aware that results may vary:
+flatpak override --user --env MOZ_ENABLE_WAYLAND=0 io.github.zen_browser.zenAlternatively, you can use Flatseal to set the environment variable:
+MOZ_ENABLE_WAYLAND=0.Disable Wayland Support Entirely:
+If the above steps don’t resolve the issue, you may need to disable Wayland support completely. Run the following command:
+flatpak override --user \ --nosocket=wayland \ --nosocket=fallback-x11 \ io.github.zen_browser.zenAlternatively, using Flatseal:
+If you’re experiencing crashes with Zen Browser on Linux using Wayland, the steps above should help mitigate the issue until an upstream fix is released in Firefox 130. We appreciate your patience and feedback as we track and address this issue.
+For any further assistance or to report new issues, feel free to reach out to the Zen Browser community.
+Thanks to eagerestwolf for creating this guide
+Original Post: Issue #296
more blabla here
+Zen is the best way to browse the web.
Beautifully designed, privacy-focused, and packed with features. +We care about your experience, not your data.
These benchmarks were performed on a device with the following specifications:
+https://browserbench.org/Speedometer3.0/
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +| Version | Score |
|---|---|
| 1.0.0-a.15-opt | TODO |
| 1.0.0-a.13-opt | 21.1 |
| 1.0.0-a.12-opt | 21.5 |
| 1.0.0-a.11-opt | 20.8 |
| 1.0.0-a.10 | 21.2 |
| Vivaldi 6.7.3329.39 | 27.8 |
| FF nightly 130.0a1 | 27.0 |
| Librewolf 128.0-2 | 20.2 |
| Version | Score | CSS | HTML5 | Page Responsiveness |
|---|---|---|---|---|
| 1.0.0-a.15-opt | 2141.63 | 59% | 91% | 90% |
| 1.0.0-a.13-opt | 1658.87 | 59% | 91% | 90% |
| 1.0.0-a.12-opt | 1874.49 | 59% | 91% | 91% |
| 1.0.0-a.11-opt | 1678.49 | 59% | 91% | 91% |
| 1.0.0-a.10 | 1660.89 | 59% | 91% | 91% |
| 1.0.0-a.9 | 470 | why | why | why |
| 1.0.0-a.8 | 446.74 | 59% | 91% | 96% |
| 1.0.0-a.7 | 1964.43 | 59% | 91% | 91% |
| 1.0.0-a.6 | 1747.98 | 59% | 91% | 91% |
| 1.0.0-a.4 | 470.49 | 59% | 91% | 97% |
| 1.0.0-a.3 | 475.52 | 59% | 91% | 97% |
| Librewolf 128.0-2 | 1953.65 | 59.66% | 89.01% | 91.72% |
| FF nightly 130.0a1 | 1912.77 | 59.66% | 90.91% | 91.72% |
We’ve took the time to make building Zen Browser as easy as possible, independent of your operating system or technical knowledge.
+ +First, you need to clone the Zen Browser repository to your local machine. This will create a local copy of the project that you can work on.
+git clone https://github.com/zen-browser/desktop.git --recurse-submodulescd desktop--recurse-submodules: This flag ensures that all submodules are cloned along with the main project. Zen Browser relies on several submodules, so this step is essential.Once you have cloned the project, navigate to the project directory and install the necessary dependencies using npm:
+npm iThis command will install all the packages listed in the package.json file, which are required for building and running Zen Browser.
To set up the browser, you need to download additional files and prepare the environment:
+npm run initThis command handles all the necessary bootstrapping tasks, such as setting up configuration files and downloading essential resources.
+Before building the browser, it’s recommended to update the American English language packs to ensure that all localization files are up-to-date:
+sh ./scripts/update-en-US-packs.shThis script updates the “en-US” localization files, which are necessary for proper language support in Zen Browser. Running this step ensures that your build includes the latest translations and language resources.
+Now that everything is set up, you can build the browser:
+npm run buildThis command compiles the source code and creates the necessary files for running Zen Browser.
+After building the browser, you can start it using:
+npm startThis command launches the browser, allowing you to see your changes in action.
Welcome to the Zen Browser FAQ section! Here, you’ll find answers to common questions and helpful tips to enhance your experience with Zen Browser. If your question isn’t covered here, feel free to explore our community forums r/zen_browser or reach out to the support team.
+Zen Browser currently lacks DRM-support, because it does not have a Widevine license. Acquiring such a license requires the payment of large fees (at least $5,000). Acquiring this license is financially unresponsible for the developer of Zen. This means that DRM-protected media cannot be played in Zen Browser for the foreseeable future. If support grows and the developer receives sufficient funding, a Widevine license may be considered.
+Feel free to support the funding of a Widevine license for Zen on Ko-Fi or Patreon!
+ + + +Zen Browser is designed with a focus on security and privacy. Additionally, the browser’s codebase is derived from Firefox, a well-known and trusted open-source project. Users can verify the safety of the browser by reviewing the source code available on GitHub . Regular updates and community engagement also contribute to its security.
+If you’d like to support the development of Zen Browser, you can do so through their official donation platforms. Contributions help the small team continue improving the browser and adding new features. You can support Zen Browser in the following ways:
+Your support helps the team maintain and enhance Zen Browser for everyone!
+If you encounter the message “Zen Browser is damaged and can’t be opened” on macOS, it is because Zen Browser is not signed with an official Apple Developer License. This triggers the Gatekeeper security feature, which prevents unsigned or unverified apps from running.
+If you encounter this error please follow our Installing Zen Browser on MacOS guide
+Ctrl keySplit x TabsYou can to enable this feature by changing a setting in the browser’s configuration. Here’s how:
+about:config page. This page contains advanced settings for the browser.toolkit.tabbox.switchByScrollingtrue by double-clicking on itOnce this setting is enabled, you can hover your mouse over the tab bar and use your mouse wheel to scroll through the tabs, making it easier to navigate between them.
+If you want to recommend features or report an issue, you can do so on the browser’s GitHub page. Before submitting your request, it’s mandatory to check if the issue or feature has already been reported. You can do this by searching through existing issues on the GitHub issues page.
+Keep in mind that the Zen Browser team is currently very small, so it might take some time for your request to be reviewed and addressed. The team is dedicated to improving the browser, but with limited resources, they prioritize the most critical and popular requests. Your patience and thoroughness in reporting can help make Zen Browser better for everyone.
+Zen Browser integrates with Firefox Sync, allowing you to sync your addons, bookmarks, history, passwords, and other browser data across multiple devices. To enable Firefox Sync in Zen Browser:
+After signing in and selecting your preferences, your data will be synced across all devices where you are signed in with the same Mozilla account.
${i(30)}
+${i(40)}
+When submitting a theme to the Zen Browser Themes Store, you can use custom preferences to define the theme’s appearance and behavior. These preferences are stored in a JSON file named preferences.json and are located in the root directory of the theme.
The following is an example of a preferences.json file:
{ "uc.example-preference.enabled": "This is an example preference", "uc.example-preference.value": "This is an example value"}Preference’s schema must be defined with a key-value pair. The key must be in the format of firefox’s preference name schema and the value must be a string, describing the preference. Right now, the only supported preference value types are booleans but that might change.
+Let’s say you have a theme that changes the background color of the browser. You can create a preference to allow users to decide whether they want a light or dark background. Here’s how you can define the preference in the preferences.json file:
{ "uc.theme.dark-background.enabled": "Enable dark background",}In the theme’s CSS file, you can use the preference to change the background color. Here’s an example:
+@media (-moz-bool-pref: "uc.theme.dark-background.enabled") { body { background-color: #000; color: #fff; }}This settings will appear on the preferences page of the theme in the Zen Browser settings. Users can enable or disable the preference to change the background color of the browser.
+ +Some preferences may require to be available only for some operating systems. For example, imagine you want an extension that hides the window’s apllication buttons (minimize, maximize, close) on Windows and linux but not on macOS, because macos doesn’t provide a way to clear them individually. You can use a prefix to specify the operating system the preference is available for.
+The prefix is the operating system name in lowercase, followed by a :.
Here’s an example of a preference that is only available on Windows and Linux:
+{ "!macos:uc.theme.hide-window-close.enabled": "Hide window close button", ...}or for another example:
+{ "windows:uc.theme.change-this-only-for-windows.enabled": "Change this only for Windows",}If you are a theme developer and would like to submit your theme, please follow these guidelines:
+Theme requirements:
+Theme Validation:
+25 characters.100 characters.PNG with a size of 300x200 (it can be resized after upload).README describing the theme and how to use it.preferences text area as a JSON object.
+Theme Submission:
+Theme Update:
+The Themes Store is a place where you can find and install themes for Zen Browser.
+If you are a theme developer and would like to submit your theme, please follow the instructions on the Submission Guidelines page.