Contact support
The best way to reach TypeSpot support is by email.
What to include in a bug report
When something isn't working as expected, including the following details can make troubleshooting much faster:
- Your Chrome or Chromium-based browser and version.
- Your operating system.
- A short description of what you expected TypeSpot to do.
- What happened instead.
- The steps that reproduce the problem.
- A screenshot, if it helps explain the issue.
Please avoid sending sensitive or private webpage information unless it is genuinely necessary to explain the problem.
Quick checks
TypeSpot does not start on a page
Refresh the page and try again. Browser extensions cannot run on some protected browser pages such as chrome:// pages, and browser security rules may restrict extension injection in other special contexts.
The wrong text element is highlighted
Move the pointer directly over the text you want to inspect. TypeSpot attempts to select the most relevant text-bearing element rather than a large parent container.
Copied typography looks different from CSS you expected
TypeSpot reports the typography values computed by the browser for the inspected element. These can differ from the exact declarations written in a stylesheet because of inheritance, browser defaults, CSS variables, and cascade resolution.
Privacy
TypeSpot is designed as a local-only utility with no account, backend, analytics, or AI service. Read the full TypeSpot Privacy Policy for details.