Skip to main content
Common questions and troubleshooting tips for the FreshJuice HubSpot DevTools extension.
There are two ways to enable the extension on a new domain:
  1. Automatic: Toggle on any debug mode (Debug Mode, Cache Buster, or Developer Mode) - the extension will automatically add that domain to your allowed list.
  2. Manual: Click the “Enable for this website” button in the popup (this appears when you visit a page with debug parameters but the domain isn’t yet in your allowed list).
Once enabled, the extension will persist your debug mode settings across page navigation on that domain.
Debug parameters will only persist if:
  1. The domain is in your allowed domains list
  2. Auto-apply to links is enabled in settings (enabled by default)
  3. Persist across sessions is enabled in settings (enabled by default)
  4. You’re navigating via internal links (not typing URLs directly in the address bar)
If parameters aren’t persisting, check your settings page and verify the domain is in your allowed list.
FreshJuice HubSpot DevTools supports:
  • Chrome (and Chromium-based browsers like Edge, Brave, Opera) - Manifest V3
  • Firefox - Manifest V3
Both versions are available in their respective extension stores:
To reset settings:
  1. Open the extension settings page
  2. Click the “Reset to Defaults” button at the bottom
  3. Confirm the reset
This will clear all your preferences, toggle states, and allowed domains.To uninstall completely:
  • Chrome: Go to chrome://extensions/, find FreshJuice HubSpot DevTools, and click “Remove”
  • Firefox: Go to about:addons, find FreshJuice HubSpot DevTools, click the three dots, and select “Remove”
Keyboard shortcuts require configuration in your browser:Chrome/Edge/Brave:
  1. Go to chrome://extensions/shortcuts
  2. Find “FreshJuice HubSpot DevTools”
  3. Set your preferred keyboard shortcuts for each debug mode
Firefox:
  1. Go to about:addons
  2. Click the gear icon and select “Manage Extension Shortcuts”
  3. Find “FreshJuice HubSpot DevTools” and configure shortcuts
Keyboard shortcuts are not set by default - you must configure them manually in your browser.
If the badge isn’t displaying:
  1. Check that Show Badge is enabled in settings
  2. Verify you have at least one debug parameter active (Debug Mode, Cache Buster, or Developer Mode)
  3. The badge only shows on HTTP/HTTPS pages (not on browser special pages like chrome:// or about:)
The badge displays a number indicating how many debug parameters are currently active on the page.
There are two ways:
  1. Quick method: Click the extension popup while on that domain and click “Disable for this website”
  2. Manual method: Go to Settings, find the domain in the “Allowed Domains” textarea, delete it, and click “Save Settings”
Removing a domain will clear all debug parameters from the current page and stop auto-applying them to links.
The extension can add three debug parameters:
  • Debug Mode (hsDebug=true) - Enables HubSpot debug mode with detailed error messages
  • Cache Buster (hsCacheBuster={timestamp}) - Bypasses HubSpot caching with a unique timestamp
  • BackOffice Developer Mode (developerMode=true) - Enables developer mode in HubSpot’s backend
You can toggle each parameter independently via the popup or keyboard shortcuts.
No. The extension does not collect, store, or transmit any personal data. All settings and preferences are stored locally in your browser using the browser’s built-in sync storage.The only data that leaves your browser is when you click links to external resources (like HubSpot documentation or the FreshJuice blog), which include UTM parameters for attribution.See the Privacy Policy for complete details.
Yes! While designed for HubSpot CMS developers, the extension works on any website. You can:
  • Add any domain to your allowed list
  • Apply debug parameters to any site
  • Use the auto-apply feature on internal navigation
The debug parameters themselves (hsDebug, hsCacheBuster, developerMode) are HubSpot-specific and won’t affect non-HubSpot sites.
We welcome feedback! To report bugs or request features:
  1. Visit the GitHub Issues page
  2. Check if your issue/request already exists
  3. If not, create a new issue with:
    • For bugs: Browser version, extension version, OS, steps to reproduce, expected vs actual behavior
    • For features: Description of the problem, proposed solution, any alternatives considered
You can also contribute code via pull requests - the extension is fully open source!

Build docs developers (and LLMs) love

Get started for freeTalk to us