Skip to content
Pickode
IT – Italiano
Pickode

License & privacy

Known limits

Every known limit of Pickode, grouped by area: pages where it can't run, exports, builders, media, analysis panels, Debug, screenshots and the library.

Updated October 20, 2026

We’d rather tell you up front what Pickode can’t do than let you find out mid-project. Here is every known limit, grouped by area, with a link to the doc that covers it.

Everywhere

  • Pickode can’t run on chrome:// pages, on the Chrome Web Store or on PDFs: browsers don’t allow extensions there. See Installation.
  • The Side Panel is available only where the browser supports it, and not in Firefox. The floating panel works everywhere. See Side Panel.

Export

  • Exports aren’t “pixel perfect” copies: stylesheets the browser can’t read because of CORS, and the page’s JavaScript, are not exported. See Export HTML + CSS.
  • The Elementor export requires Flexbox Containers, on by default in recent Elementor versions. See Elementor.

Assets, Lottie and video

  • Lottie previews don’t run After Effects expressions. See Assets and media.
  • Very long videos need a lot of memory to save. DRM-protected video, encrypted streams, live streams and YouTube are not supported. Download only content you own or are authorized to use. See Streaming video.

Analysis

  • The WordPress panel sees only the plugins that leave traces in the frontend. See WordPress.
  • In the accessibility audit, axe’s detailed messages stay in English (rule titles are translated). See Accessibility.
  • GEO: sites with anti-bot protection may answer Pickode differently than they answer real crawlers. The GEO score is indicative: no tool can guarantee that an AI will cite you. See GEO.

Screenshots and Responsive

  • Full-page screenshots follow the document’s scroll, and are limited to about 32,000 px in height. See Screenshots.
  • In Responsive, sites that require a login may not see your cookies. See Responsive.

Debug

  • In Chrome, cookies are removed for the whole domain, subdomains included.
  • In Firefox, the HTTP cache can’t be cleared for a single site.
  • The image optimizer can’t read images protected by a login or anti-hotlinking.

See Debug.

Library

  • Without Google Drive sync, the library lives only in the browser where you saved it. See Library.

Still stuck?Contact us