Extensions
Why an extension doesn't work in Step
Most Chrome extensions work in Step. The few that don't usually rely on Google account features.
1 min read
Step runs the same extension API as Chrome. Compatibility issues are almost always limited to extensions that depend on a Google account session inside the browser.
Site access permission
Open the extension's details and check Site access. Some extensions need On all sites; others need to be granted site by site.
Google account dependency
Extensions that read your Google account state (Drive picker integrations, Gmail-aware tools) may misbehave. Sign in to the Google service in a tab first.
Manifest V3 reality
Step uses Chromium's MV3 enforcement. A handful of MV2-only extensions are blocked. Look for an MV3-compatible alternative.