Noxri is built on parts of Dark Reader's MIT-licensed open-source code, including important pieces of page analysis and dynamic theme generation. It then adds its own native app, Safari extension workflow, configuration bridge, themes, and per-site model. Dark Reader remains the upstream project and serves several browsers; Noxri packages an adapted rendering layer into an iPhone- and iPad-focused Safari product. Comparing the products therefore starts with architecture and workflow, not an invented story about two unrelated engines.
Scope and review date
This comparison was reviewed on July 13, 2026. It uses Noxri 2.6.0, the current Noxri Swift and TypeScript implementation, Dark Reader's official Safari documentation, and the upstream Dark Reader repository and MIT license.
No controlled same-device test of both Safari products has been published yet, so this article leaves speed and overall website coverage unranked. Versions, settings, site-fix data, Noxri adaptations, and Safari itself can all change the result.
How the products relate
| Layer | Noxri | Dark Reader |
|---|---|---|
| Rendering foundation | Uses and adapts Dark Reader open-source rendering code | Maintains the upstream open-source project |
| Product focus | Native app plus Safari Web Extension for iPhone and iPad | Browser extension available across major browsers, with a Safari product for iPhone, iPad, and Mac |
| Configuration | Noxri app model mapped into extension settings | Documented extension settings and per-site interface; private Safari storage details are not assessed |
| App-extension communication | Native messaging and shared app-group configuration | Depends on the official build and browser platform; no claim is made here about private Safari internals |
| Per-site behavior | Global settings with site mode, theme, pause, PDF, and native-dark overrides | Global and per-site theme configuration |
| Themes | 10 Noxri presets, including dark and light reading themes | Presets plus direct color and appearance customization |
| Site compatibility | Bundled detection hints and site-fix resources, with Noxri-specific adaptations | Upstream site-fix lists maintained with Dark Reader releases and optional update mechanisms |
| Best fit | Safari users who want Noxri's native app workflow and curated product model | Users who value the upstream project, broader browser availability, and extensive extension controls |
What Noxri inherits from Dark Reader
Dark Reader is an open-source browser extension that analyzes pages and generates dark styles. Its repository includes dynamic theme code, color modification, CSS variable handling, image analysis, native-dark detection, multiple rendering modes, and site-specific fixes.
Noxri's JavaScript and TypeScript layer retains substantial Dark Reader concepts and code. The repository still contains the dynamic-theme modules, detector configuration, site-fix formats, and many Dark Reader identifiers. Noxri also includes Dark Reader's MIT license in the app's open-source licenses screen.
Credit matters here. Dark Reader's maintainers and contributors built part of Noxri's rendering foundation. Saying so also prevents Noxri from taking credit for an inherited mechanism and then presenting that same mechanism as a weakness in Dark Reader.
MIT licensing permits use and modification under its license conditions. It does not make Noxri an official Dark Reader product, and it does not mean the finished products have identical behavior.
For a rendering-level explanation, read CSS Filter vs Dynamic Theme. That distinction is more useful than pretending every dark-mode product starts with a completely different algorithm.
What Noxri adds around the rendering engine
A native configuration model
Noxri defines its global settings, site settings, automation, and built-in themes in the native app. The model includes a global mode, system- or time-based automation, a current theme, native-dark and PDF behavior, and a map of per-site overrides.
That app model is translated into the effective settings used by the JavaScript rendering layer. A site can inherit the global configuration or override its mode, theme, pause state, native-dark preference, and PDF behavior.
A bridge between the app and Safari extension
The native app and Safari Web Extension exchange configuration through Safari native messaging and shared app-group storage. The extension can request the current native configuration. Site changes made from the extension can be merged back into the shared site map so the native app can reflect them.
This is more than changing the color transformation formula. It is product infrastructure for keeping two Apple-platform control surfaces aligned: the main app for broad configuration and the Safari extension interface for the current website.
Cached startup followed by native refresh
The extension can load its local cached configuration and apply it before completing a refresh from the native app. That order is intended to reduce the gap between a page opening and the correct Noxri configuration becoming available. When the native configuration arrives, Noxri compares it with the current extension state and reapplies settings only when needed.
This startup sequence is a Noxri adaptation around the rendering engine. Its value has to be checked during navigation and resume testing; it is not a guarantee that every page will avoid a flash or rendering error.
A curated Noxri theme and site model
Noxri currently supplies 10 built-in themes and treats Sepia and Mint as light reading themes. It also exposes per-site mode, theme, temporary pause, and native-dark decisions through the same configuration model.
Dark Reader offers its own presets and more direct appearance controls. The difference is not that one product has themes and the other does not; it is how those themes and site choices are packaged and maintained for the intended user.
Why “Dark Reader is only JavaScript” is too simple
The upstream Dark Reader project is primarily a TypeScript and JavaScript WebExtension codebase, but Dark Reader is still a complete browser-extension product, not merely a color function. It has its own user interface, settings, site lists, release process, per-site controls, documentation, and Safari distribution.
Dark Reader's official Safari version supports iPhone, iPad, and Mac on the Apple systems listed by its current documentation. Its wider project also serves Chrome, Firefox, Edge, and other supported browser environments. That cross-browser scope is a real product advantage for someone who wants similar controls outside Safari.
The cleanest description is:
- Dark Reader develops the upstream cross-browser extension and rendering system.
- Noxri adapts that open-source rendering foundation inside a separate Safari-focused product with its own Swift app, configuration model, native bridge, themes, purchase flow, and compatibility decisions.
This article stops at what Dark Reader's official site and public repository document. It does not speculate about private implementation details in the current App Store build.
Native dark mode and site fixes
Both products contain more than generic color conversion. They need to detect when a website already offers dark mode and apply exceptions when a page's structure defeats the general algorithm.
Noxri ships detector hints, a native-dark-site list, dynamic-theme fixes, inversion fixes, and additional site assistance. Dark Reader's public repository also documents site fixes and how updates are distributed with releases or through its optional synchronization setting.
Because Noxri begins with Dark Reader-derived mechanisms, a site fix cannot automatically be described as unique to Noxri. A technical article must trace whether a rule comes from the upstream project, was changed by Noxri, or is Noxri-specific before making that claim.
How a Safari Extension Detects a Website's Native Dark Theme and How Dark Mode Extensions Protect Images and Video cover two of the most visible parts of this pipeline.
Which product should you choose?
Choose Noxri if
- Safari on iPhone and iPad is your main target.
- You want a native app for global settings and a Safari control surface for the current site.
- You prefer Noxri's curated themes and explicit system or time automation.
- You want to test the full product during its seven-day trial before choosing monthly or lifetime access.
- Noxri's current site adaptations work well on the pages that matter to you.
Choose Dark Reader if
- You want the established upstream project rather than a product built from an adapted fork.
- You use several browsers or want a broader cross-browser workflow.
- You prefer Dark Reader's own presets and direct appearance customization.
- You want upstream documentation, source history, issue tracking, and community contributions.
- Dark Reader already handles your important sites well.
The shared lineage makes matched testing more important, not less. Use the same device, Safari version, page state, and comparable settings. Test first load, navigation, back-forward restoration, native-dark sites, images, video, and at least one complex interactive page.
Limits of this comparison
Noxri does not get a blanket “better engine” claim here. A Noxri adaptation may also exist in a newer Dark Reader release, while a shared code foundation does not make the finished products identical.
It also does not rank performance, website coverage, or update quality without a controlled current test. Those claims need published methods, matched screenshots, version labels, and results that readers can inspect.
For a comparison between two independently developed Safari products, continue with Noxri vs Noir.