Signed-in pages
Local uses the session in your Chrome profile without exporting website cookies. Cloud uses separately approved supported site connections.
CHOOSE WHERE CHECKS RUN
Your browser checks. PageFluxer keeps you informed.
Monitor website changes locally in Chrome with PageFluxer Local. Keep website cookies on your device and send selected captures for history and notifications.
PageFluxer Cloud + Local · Shared rules, history and notifications
Supplier availability · illustrative workflow
- Choose
- Select the stock label and price.
- Check
- Use Local with your existing Chrome session.
- Notify
- PageFluxer delivers the matching update through your enabled channels.
Illustrative example. A successful first test creates a quiet baseline.
Match the check location to the page.
Prices, stock and text
Share CSS targets, supported AND conditions, price and stock rules, and new-link monitoring across Cloud and Local.
History and notifications
Review retained captures and configure email or eligible webhook, Slack and Teams delivery in PageFluxer.
FROM QUESTION TO CAPTURED CONTEXT
A practical way to start.
Choose Cloud or Local
The extension can start either. Cloud drafts finish in the app with independent validation; Local tests execute in your browser.
Test and save
Confirm selected values, your rule and the check interval. The test establishes a quiet baseline.
Review the changes
Later matching changes use your existing PageFluxer history and notification pipeline.
FIT IT TO YOUR WATCH LIST
Separate allowances for Cloud and Local checks.
Local includes 10 / 50 / 200 / 500 saved monitors on Free / Starter / Pro / Business, at 5 / 2 / 1 / 1 minute minimum intervals. Paused Local monitors still use slots.
Local uses no Cloud check credits. Selected-capture size, daily upload count and byte limits apply, with shared history and notification allowances. PageFluxer Cloud retains its Cloud HTML and Cloud Browser limits.
Compare plan allowances →Common questions
Can I close the original page tab?
Yes. Local opens temporary inactive tabs as needed. Chrome must remain running on an awake desktop. Cloud checks continue even when Chrome is closed.
Does Local share my cookies or authentication details?
The extension does not export website cookies, authorization headers or browser storage. Selected captures, URLs, titles, settings and explicitly recorded non-sensitive values are sent to PageFluxer. Selected content may still be private.
Do both modes support every feature?
The rule model is shared where supported. This Local release supports selected webpage text and links with safe DOM preparation. Screenshots, PDFs, source watches, AI processing and no-change alerts remain Cloud features. Native key presses and foreground-dependent pages are unsupported locally.
Put it to work.
Explore a related workflow or the controls behind the capture.
Start with a page you already keep checking.
Confirm the capture where your monitor will run, then choose the settings that match your goal.