Learn the model before changing your data.
Support · Crest field desk
Find your way
forward.
Start with the shortest path below. If Crest still feels lost, bring the details that help identify the exact device, Space, page, and moment.
Reload the page or reopen only the affected Space.
Device, OS, Crest version, Space, and exact steps.
Start here
Use the smallest reset
that fits the problem.
Reload the affected page first. If only one Space is involved, switch away and back. If a page remains unresponsive, close that tab and open it again. Relaunch Crest only after those focused steps fail.
Before clearing history, website data, passwords, or a Space, confirm that the problem is not limited to one page or one signed-in account. Those actions remove useful state and may not address a compatibility issue.
Open the Crest field guide01
Spaces own their data.
If a tab, sign-in, password, permission, or history item seems missing, verify the active Space first. Each Space has separate website data, Keychain items, history, permissions, tabs, extensions, and synchronization state. The Spaces of a Sub-Space group share their website data, passwords, history, permissions, and extensions. On Mac, Chromium and WebKit keep separate website data, so a site you signed in to in one engine may ask you to sign in again in the other.
For sync issues, open Settings → Sync on both devices and compare the selected iCloud account, Space list, last sync state, and per-Space password-sync switches. Cookies, website data, downloads, and active page state remain device-only.
02
When one website behaves differently.
Reload the page, confirm content blocking and permissions for that site, and try the same page in a new tab inside the same Space. If the issue follows only one Space, compare its content-blocking and extension settings.
On Mac, try the page in the other engine: choose Page → Open Page in WebKit or Open Page in Chromium. If it works there, change Opens in in Site Controls to keep the website on that engine, and mention both engines in your report. Extensions run only on Chromium pages, and protected video plays in WebKit. Crest on iPhone and iPad uses WebKit.
03
Review before importing.
Mac import is optional. Crest shows supported browsers and a Space-by-Space before-and-after review before adding tabs, bookmarks, folders, profiles or Spaces, and supported passwords.
Passwords are stored in the system Keychain. If a password is unavailable, confirm the correct Space and device, then check Settings → Passwords and the Space’s iCloud Keychain sync switch. Never post a password, private URL, recovery code, or account token in a public support request.
04
Bring a trail someone else can follow.
Include the Apple device model, operating-system version, Crest version, the page’s engine on Mac, active Space, the page or feature involved, exact steps, what you expected, and what happened instead. A screenshot is useful only after removing private tabs, account details, URLs, and messages.
Community, questions, and compatibility
Use r/CrestBrowser for questions, feedback, early ideas, and website or extension compatibility discussion. Reddit is public; do not include passwords, account details, private URLs, browsing history, or other sensitive information.
Reproducible engineering reports
Use GitHub Issues when you can provide a Crest version, Apple platform, repeatable steps, expected result, and actual result. Suspected security vulnerabilities belong in a private report, never Reddit or a public issue.
Chat and quick questions
Join the Crest Discord to ask questions, share ideas, and talk with other people using Crest. Discord is for discussion; bugs you can reproduce belong in GitHub Issues so they can be tracked. Do not post passwords, account details, or private URLs.