Crypto Price Alerts: Browser Notifications, No Account

Crypto prices do not wait for anyone. If you want to buy Bitcoin at a specific level or sell Ethereum when it hits your target, you either stare at a chart all day or you let a tool watch for you. This page is that tool, stripped to the minimum that actually works. Pick a coin, choose above or below, set the target, and the browser takes care of the rest as long as the tab stays open.

Everything runs on your device. There is no account, no email capture, no server that remembers your alerts. If privacy matters to you (and for price targets that reveal your trading intent, it probably should) this is the cleanest implementation of crypto alerts you will find. The tradeoff is explicit: alerts only fire while the tab is open, because nobody else is checking for you. For most users that is a fair deal. For high frequency traders it is not enough and you should use a dedicated exchange with server side alerts.

If you also want a quick read on where the market is heading while you wait for your alerts, the live prices page shows the top 250 coins with 24 hour changes, the market overview has total market cap and dominance, and the crypto fear and greed index is a one number sentiment gauge.

How It Actually Works

The page above stores your alerts in your browser’s localStorage under a single key. When it loads, it reads the stored alerts, builds a deduplicated list of coin ids, and starts a polling loop that hits our cached CoinGecko proxy every 60 seconds. Each poll returns the current USD price for every coin you have an active alert on, in a single request. The client then checks every armed alert against the new price and fires a notification for any that have hit their target.

Permission Model

Browser notifications are opt in by design. The very first time you click enable alerts on the page, your browser pops up its own permission dialog and asks whether this site can show notifications. Grant it once and the page can fire notifications until you revoke permission in your browser settings. Deny it and the page falls back to an in page banner, which still works when the alerts tab is the one you are looking at but will not reach you on another tab.

The permission request has to happen in response to a click, because browsers do not allow sites to ask for notifications at page load. That is why the enable button exists as a deliberate step rather than an automatic prompt. It is not a design choice on our end, it is a browser requirement.

Polling Cadence

Every 60 seconds is a deliberate middle ground. Faster polling would burn CoinGecko quota without delivering better alerts, because the price data itself is updated at a similar cadence upstream and we cache at our edge for 60 seconds too. Slower polling would leave obvious gaps where a price could touch a level and retreat without firing. One check per minute is how most mainstream alerting tools work and it is plenty for any decision you should be making on a browser alert.

If the tab is inactive, modern browsers may throttle background JavaScript to save battery, which can stretch that interval out. The page is robust to this: it records the last poll time and fires a catch up check the moment the tab becomes visible again, so you will get your alert the first time the tab is foregrounded after the target is hit.

Triggered Alerts

When an alert hits its target, three things happen in order. The page fires a browser notification with the coin name, the direction, and the price. The page shows an in page banner at the top confirming the trigger. The alert itself moves from armed to triggered in your list, timestamped, and stops polling. A triggered alert will not fire again on its own. You can delete it if you are done, or re arm it to check against a new target.

This design is deliberate. Repeating notifications at the same price level every minute would be worse than no notifications at all. One fire per alert is the right default.

When This Tool Is Enough, and When It Is Not

This is a simple, private, free price alert tool that runs entirely in your browser. It is great for a lot of real use cases and it is not a replacement for a trading terminal. Knowing the difference will save you from misusing it.

When It Is Enough

If you are watching for a medium term entry or exit level, this is exactly the right tool. Something like set an alert for Bitcoin at 80,000 so I know when to re enter my position. Polling once a minute is fast enough for that kind of decision, the zero friction setup means you can add alerts in seconds, and the local only storage means nobody else sees your price targets. No email capture, no account bloat, no selling your data.

It is also good for long term milestone alerts. If you want a heads up when Ethereum reaches a new all time high, or when your favourite altcoin doubles, this tool will tell you when it happens and you can come back to check the chart. Setting and forgetting alerts is the point. You do not need a trading terminal for this.

When It Is Not

If you are trying to scalp short term moves where seconds of latency matter, this is the wrong tool. A 60 second polling interval plus browser notification latency plus the time it takes you to react is way too slow for anything high frequency. Use an exchange with WebSocket price feeds and server side alerts for that.

If you need alerts that fire when you are away from your computer, this is also the wrong tool. Browser tabs need to be open and the browser needs to be running. If you want SMS or email alerts that work when your laptop is off, you need a service with a server. This page does not pretend to compete with that.

And if you want alerts on exotic conditions (funding rate spikes, liquidations, on chain events) you need tools that ingest that data directly. This page only knows what CoinGecko publishes, which is spot prices and 24 hour changes. That is plenty for most retail use, but not for every use.

Tips for Getting the Most Out of It

A few small habits make this tool a lot more useful than it looks at first glance.

• Stack alerts to define ranges. Want to know if Bitcoin breaks out of a consolidation zone? Set an above alert at the top of the range and a below alert at the bottom. Whichever direction it moves, you find out first.
• Use the price shown in the form as a sanity check. The current price appears next to the target field after you pick a coin. If you meant to set a target slightly below current price but accidentally entered a number above it, the form catches the mismatch before saving.
• Pin the tab. Pinned tabs in Chrome, Firefox, and Safari are less likely to be throttled or suspended when the browser is under memory pressure, which keeps alerts reliable. Open the alerts page in a pinned tab and leave it there.
• Grant notification permission once, on purpose. If you accidentally click deny, your browser will stop asking and you will have to go into site settings to re enable. It is a minor annoyance but worth being deliberate the first time.
• Re arm when a target is hit but you still want to watch. If an alert fires at 100,000 and you want another alert at 110,000, you can either delete and recreate, or use the re arm button on the triggered alert and edit the target. Either works.
• Do not rely on this for anything where a missed alert is a disaster. Browser tools can always fail (permission revoked, tab suspended, browser crashed, power loss). For critical trades use exchange side alerts or a server backed service in addition to this one.

Why Client Side

The obvious question is why not just run a server that keeps checking prices even when you are offline. The short answer is that doing that well is expensive, invasive, or both, and most people do not actually need it.

Expensive because a server side alerting system has to poll prices for every user, store every user’s alerts in a database, and push notifications out reliably, which means engineering around retries, rate limits, authentication, email deliverability, and all the other infrastructure that comes with owning user state. Doing this cheaply compromises reliability. Doing it reliably costs money that has to come from somewhere, usually ads, upsells, or data resale.

Invasive because a server that knows your alerts also knows where you think prices are going. That is extremely valuable data. It tells an operator exactly which levels retail traders are watching, which means it can be used to front run orders, inform market making, or be sold to anyone willing to pay. Even if an operator promises not to do any of that, the data exists and someone could do it in the future. The only way to be sure your alert targets are private is for them to never leave your device.

Client side is the compromise that gets you real utility without either of those costs. You give up alerts when the tab is closed. In return you get a tool that is free, private, instant to set up, and cannot be abused because there is nothing to abuse. For most users that trade off is the right one.