Orbit FAQ

Start with the question that matters to your setup. These answers describe the tools as they work today.

Randomness

Is Orbit random? Wheel, Roulette, Coin and direct-selection tools use browser Web Crypto to choose a result before revealing it. Physical Dice, Plinko, Ball Draw and Marble Race use Web Crypto to seed starting conditions, then measure the simulated result. A physical board or course can affect its distribution; Plinko does not promise equal lane probabilities. When enabled, positive wheel weights determine proportional chances. A streak is possible and does not change the next independent selection.

Privacy and local data

Do I need an account? No. Where are wheels stored? Metadata and history use localStorage, while wheel images use IndexedDB. Utility settings, histories and compact team images use a separate localStorage record. Another device or private-browsing session has different data. There is no automatic upload of your entries.

Images and sharing

Can I add images? Wheel, custom Roulette and Team Generator support images. Upload PNG, JPEG, WEBP or SVG; SVG is converted to a bounded raster image rather than executed. Images are resized and compressed, so keep your originals separately.

Can recipients edit a remote wheel? Its snapshot is read-only, but Make a copy creates their own editable local version. Later edits to your original do not update a published snapshot. Anyone with the link may access it. Number, dice and answer setup links include settings only, with no result history.

Offline and backups

Does Orbit work offline? Local tools and help pages do after an online visit and service worker activation. Creating a remote share, deleting one or opening a previously unfetched remote snapshot needs a connection. A .orbit file is a full downloadable backup of local workspace data, referenced images and the new utilities. Restore replaces local workspace data, so export a current backup before restoring another.

Choosing a mode