Upgrade to Pro
Upgrading to Pro unlocks the full set of pageflare optimizations: critical CSS, self-hosted Google Fonts, YouTube facades, hash filenames, platform image CDN rewrites, and more.
Step 1 — Purchase a license
Section titled “Step 1 — Purchase a license”Go to pageflare.dev/pricing and select the Pro plan. Complete checkout with your preferred payment method. After payment you will receive a confirmation email and your account portal will show an active Pro license.
You do not need to download anything new — the same CLI binary you already have will unlock Pro features once a license is activated.
Step 2 — Activate on your machine
Section titled “Step 2 — Activate on your machine”Run the login command:
pageflare --loginOpening browser for authentication… Waiting for license token… License activated tier=pro expires=2026-04-11 Saved to ~/.config/pageflare/license.json
The CLI opens your browser, you authenticate with your pageflare account (the same email used at checkout), and the token is saved automatically to ~/.config/pageflare/license.json. No copy-paste required.
Step 3 — Activate in CI/CD
Section titled “Step 3 — Activate in CI/CD”For automated environments, copy your token from pageflare.dev/account and store it as a secret in your CI provider:
# Any CI environmentPAGEFLARE_LICENSE="<your-token>" pageflare dist/ --output dist/See License Management for provider-specific instructions (GitHub Actions, GitLab CI, Netlify, Cloudflare Pages, Vercel).
Step 4 — Verify Pro features are active
Section titled “Step 4 — Verify Pro features are active”Run pageflare on your build output and check the features line in the summary:
pageflare dist/ --output dist/pageflare → dist/ Done 312.8 KB saved (51.4%) 2.1s Files 42 total, 42 optimized, 0 unchanged, 0 errors Size 608 KB → 295 KB Features ✓ minify_html ✓ minify_css ✓ minify_js ✓ js_defer ✓ lazy_images ✓ img_dimensions ✓ font_swap ✓ self_host_fonts ✓ critical_css ✓ youtube_facades ✓ hash_filenames ✓ platform_images ✓ speculation_rules
All Pro features show a ✓. If any remain ✗, run pageflare --license to confirm the license is detected correctly.
pageflare --licenseLicense pro Expires 2026-04-11 (30 days) Source ~/.config/pageflare/license.json
Before and after comparison
Section titled “Before and after comparison”The table below shows typical payload and score improvements when moving from Free to Pro on a content-heavy site:
| Metric | Free | Pro |
|---|---|---|
| Total page weight | 608 KB → 420 KB | 608 KB → 295 KB |
| Bytes saved | ~31% | ~51% |
| Render-blocking resources | Reduced | Eliminated (critical CSS) |
| Third-party font requests | Present | Eliminated (self-hosted) |
| YouTube embed on load | Full iframe | Facade only |
| Cache hit rate on redeploy | Low | High (hash filenames) |
| Image CDN transforms | None | Automatic |
The exact numbers depend on your site’s content. Sites with many images, Google Fonts, and YouTube embeds see the largest gains.
Troubleshooting
Section titled “Troubleshooting”Pro features show ✗ after activation
Check the license source:
pageflare --licenseIf the output shows tier=free or Source: none, the token was not found. Ensure:
~/.config/pageflare/license.jsonexists and is readable, orPAGEFLARE_LICENSEis set in the current shell / CI environment
Login command opens wrong account
The browser will use your default profile. If you have multiple browser profiles, make sure you are signed in to the pageflare account associated with your purchase.
License not recognized in CI
Confirm the secret is available in the job step. In GitHub Actions, secrets are not inherited by pull requests from forks by default. Use pageflare --license as a debug step to print what the CLI sees.
Next steps
Section titled “Next steps”- Read License Management for renewal, multi-machine, and team workflows.
- Review the full Feature Comparison to see every optimization now available to you.
- See the CLI reference for flags that control which Pro features run.