Troubleshooting Common Issues

Solution 1: Check Page Type

TLD2 works best with article-based content. It may fail on:

• Login/paywall pages
• Search results or index pages
• Single-page apps (SPAs) with dynamic content
• PDFs or embedded documents

Fix: Ensure you're on an actual article page, not a landing page or index.

Solution 2: Wait for Page to Fully Load

If the article loads content dynamically via JavaScript, TLD2 might extract before content appears.

1. Wait for the full article to appear on screen
2. Scroll down to trigger lazy-loaded content
3. Then activate TLD2

Solution 3: Disable Conflicting Extensions

Other extensions can interfere with content extraction.

1. Open chrome://extensions
2. Temporarily disable ad blockers, reading mode extensions, or content modifiers
3. Refresh the article page
4. Try TLD2 again

Solution 4: Refresh and Retry

Simple refresh often resolves transient issues:

1. Press Ctrl+R (Windows) or Cmd+R (Mac)
2. Wait for page to fully load
3. Click TLD2 extension icon

Solution: Page Has Non-Standard HTML

Some pages use unconventional markup that confuses Readability.js.

Workaround: Try using reader mode (if available) first, then TLD2. Or manually copy the article text and use a different summarization tool.

Report: Send the URL to 0xdespot@0xdespot.com to help improve extraction for that site.

Solution 1: Check Browser Audio Permissions

1. Go to chrome://settings/content/sound
2. Ensure sound is not blocked for tld2.io or chrome-extension:// URLs
3. Check "Not allowed to play sound" list—remove TLD2 if listed

Solution 2: Verify System Volume

• Check system volume is not muted
• Verify correct audio output device selected
• Test audio with another tab (e.g., YouTube) to confirm speakers work

Solution 3: Check Other Tabs

Chrome allows only one tab to play audio at a time by default.

• Pause audio/video in other tabs
• Close tabs playing music or podcasts
• Try TLD2 again

Solution 4: Manually Trigger Playback

1. Open TLD2 settings
2. Disable "Auto-play"
3. Save settings
4. Summarize an article
5. Manually click the play button

This helps diagnose if the issue is with auto-play specifically.

Solution 5: Check Console for Errors

1. Press F12 to open DevTools
2. Go to the Console tab
3. Trigger TTS playback
4. Look for red error messages related to AudioContext, ONNX, or WebGPU

Common errors and fixes:

• AudioContext suspended → User interaction required; manually click play
• Failed to load ONNX model → Clear browser cache and reload
• WebGPU initialization failed → See GPU troubleshooting below

Solution: Enable Pitch Correction

1. Open TLD2 settings
2. Find "Pitch Correction" toggle
3. Enable it (checkmark should appear)
4. Save settings

Pitch correction automatically adjusts pitch inversely to speed, maintaining natural intonation at any playback rate.

Alternative: Manually adjust the pitch slider until voice sounds natural.

Solution: Your System is Using CPU-Only (WASM) Mode

This is expected if you don't have a GPU or WebGPU isn't enabled. See GPU Detection Issues section below for how to enable GPU acceleration.

Workaround if GPU unavailable:

• Use shorter summary lengths (Short instead of Long)
• Close resource-heavy browser tabs
• Be patient—WASM mode is functional, just slower

Solution 1: Update GPU Drivers

NVIDIA:

1. Visit nvidia.com/drivers
2. Download latest drivers for your GPU
3. Install and restart computer

AMD:

1. Open AMD Software Adrenalin
2. Check for updates
3. Install and restart

Intel:

1. Download Intel Driver & Support Assistant
2. Scan for driver updates
3. Install and restart

Solution 2: Enable Hardware Acceleration in Chrome

1. Go to chrome://settings
2. Search for "hardware acceleration"
3. Enable "Use hardware acceleration when available"
4. Click "Relaunch"

Solution 3: Enable WebGPU in Chrome Flags

1. Go to chrome://flags
2. Search for "WebGPU"
3. Set "Unsafe WebGPU" to Enabled
4. Restart Chrome

Solution 4: Check GPU Status

1. Navigate to chrome://gpu
2. Search for "WebGPU" on the page
3. Look for "WebGPU: Hardware accelerated"
4. Check "Problems Detected" section for blocklisted GPU

If GPU is blocklisted, try: chrome://flags/#ignore-gpu-blocklist → Enable (use with caution).

Solution: Resource Management

• Close unused tabs before summarizing long articles
• Disable other resource-heavy extensions temporarily
• Use shorter summary lengths
• Ensure your computer isn't thermal-throttling (check fans/heat)

Solution: Click "Save" Button

Settings changes are not applied until you click the "Save" button at the bottom of the settings panel.

1. Make your changes
2. Scroll to bottom of settings panel
3. Click "Save"
4. Wait for "Settings saved" confirmation

Solution: Verify Key Format

• Gemini API keys start with AIza followed by 35 alphanumeric characters
• Ensure no spaces before or after the key when pasting
• Verify you copied the entire key from Google AI Studio
• Try regenerating a new key if problem persists

Solution: Clean Reinstall

1. Go to chrome://extensions
2. Find TLD2 and click "Remove"
3. Restart Chrome completely
4. Visit Chrome Web Store
5. Reinstall TLD2

Solution: Check Chrome Version

TLD2 requires Chrome 120 or newer.

1. Go to chrome://settings/help
2. Check your Chrome version
3. Update if below version 120