WebToSparkUnsupported or empty page
Chrome internal pages, the Web Store, other extensions and the PDF viewer block injection. Sensitive routes such as messages, login and billing are excluded. GitHub automatic extraction is limited to Trending routes. For an ordinary page outside adapter coverage, try the explicit current-page export where available.
Reload sleeping tabs yourself. WebToSpark does not wake discarded tabs without fresh cache. Wait for the page to render, then parse again.
Missing comments or a shorter export
Expand and load the needed content yourself before exporting. Ordinary export never scrolls or loads replies. Virtualized lists can remove older content from the DOM, so scrolling through a page does not ensure it all remains capturable. A partial warning or smaller capture needs inspection.
Site redesigns can break adapter selectors. A sanitized test fixture does not establish current compatibility with every live page.
No file or unknown result
Check Chrome’s downloads and the selected directory. Reauthorize directory access in Options if needed. For Native Host, test the connection and output root, and check the 32 MiB file limit. If the result is unknown, inspect files before making another copy or releasing a reservation.
Prepare a useful report
Include extension version, Chrome version, operating system, page type, selected formats, save target, exact error and minimal reproduction steps. A public URL is useful only if you are comfortable sharing it. Remove private content, license tokens, API keys and personal paths. Diagnostics remain local unless you choose to share them.