Compatibility guide

Know where Redline can work—and where the browser draws the line.

Supported desktop browsers, integration differences, protected pages, keyboard shortcuts, and current product limitations.

Redline 1.0.3 is designed for desktop browsing and research. Browser capabilities shape how the side interface opens and which readable page content is available, but the local vault and research model remain the same.

Supported browsers

BrowserSupportPrimary interface
Google ChromeCurrent desktop releaseChrome side panel and library tab
Microsoft EdgeCurrent desktop releaseChromium side panel and library tab
BraveCurrent desktop releaseChromium side panel and library tab
Other Chromium buildsBest effort on current compatible releasesBehavior depends on WebExtensions and side-panel support
Mozilla FirefoxDesktop Firefox 142 or laterSidebar with a tab fallback where needed
Mobile browsersNot supported in Redline 1.0.3None

Install Redline from the marketplace that matches your browser. Support may ask you to reproduce a problem on the current stable browser release.

Updates should be automatic.If the version shown on your extension details page is behind the latest release, open Redline’s Chrome Web Store or Firefox Add-ons listing and check for an update. Reinstall only as a last resort, and first create and safely store a Library → Exports → All data → JSON backup.
Bring bookmarks to either buildRedline can import Chrome-family bookmarks HTML or JSON created with Firefox’s bookmark manager Import and Backup → Backup option. This browser-bookmark migration is separate from importing a Redline All data JSON backup.

Protected and unsupported pages

Browsers prevent extensions from running on some surfaces. Redline cannot preserve readable evidence, capture annotations, or restore highlights on browser settings, extension stores, extension-management pages, new-tab surfaces, many built-in PDF viewers, and other protected URLs.

Embedded documents, cross-origin frames, canvas-based readers, and pages that replace native text selection may also limit capture even when the top-level page itself is available.

Quick testIf a capture action fails, reproduce it on a normal public https:// article. If Redline works there, the original surface is likely protected or structurally incompatible.

Permissions and browser integration

CapabilityWhy Redline needs itBoundary
Website accessUser-initiated readable capture, selection capture, highlight restoration, and local page metadataNo browser-internal protected pages
Active tab and tabsCurrent title, URL, capture context, and content-script communicationNot a browser-history database
Context menusRight-click page, selection, link, and image captureOnly when the user chooses an action
DownloadsPass locally generated exports to the browser download flowNo automatic upload or remote backup
Local storageVault records, source captures, settings, and view synchronizationSpecific to the current browser profile

See the full privacy policy for the data-access and retention model.

Keyboard shortcuts

ActionWindows / LinuxmacOS
Save current pageCtrl + Shift + SCmd + Shift + S
Open sidebarCtrl + Shift + YCmd + Shift + Y
Open libraryCtrl + Shift + LCmd + Shift + L

A browser, operating system, or another extension can reserve the same keys. Use the toolbar and browser extension-shortcut settings when a shortcut conflicts.

Known limitations in Redline 1.0.3

Highlight restoration follows the current page

Restoration depends on the saved text and nearby context still existing in a compatible document. Rewritten text, duplicated passages, client-side navigation, embedded viewers, or major layout changes can require review or prevent a match.

Local storage belongs to one profile

Redline does not synchronize profiles or devices. Clearing the relevant profile data or uninstalling the extension can remove the vault unless you created an All data JSON backup. Import restores vault records but keeps destination settings and does not include Domain Notes, view preferences, or Local Export History.

Readable witnesses are not complete page archives

Source Witness stores normalized readable text and capture metadata after an explicit user action. It does not retain scripts, styles, forms, cookies, login state, third-party assets, every network response, or a pixel-perfect rendering. Dynamic or application-like pages can produce an incomplete or unavailable comparison.

Citation metadata needs review

Websites often publish incomplete or inconsistent metadata. Generated fields and bibliography lines should be checked before formal use; style-like bibliography output is not guaranteed to be fully style-guide compliant.

Browser side interfaces differ

Chrome-family browsers and Firefox expose different side-panel and sidebar APIs. Redline falls back to an extension tab only when neither compatible interface is available.

Report a compatibility problem

Before reporting, record the exact Redline version, browser and version, operating system, page type, and whether the issue reproduces on a non-sensitive public page. The local support summary builder can format these details without submitting them.

Keep reports public-safe.Do not attach a Redline export, browser profile, private URL, selected research text, credential, token, or unredacted screenshot.