A Tasbih Counter is a focused digital counter that runs entirely in your browser, lets you pick one of two round targets (33 or 99), and tallies your entries one tap at a time while marking each completed round on screen. It does not prescribe rulings, supply recitation text, or rate your practice — it just keeps the number honest so your attention stays on the words you choose to count. Moving from a physical misbaha to a digital one changes almost nothing about how you count; moving from another counter app tends to simplify the surface, since this page keeps state, history, and exports on a single screen. There is no account to create, no file to download, and nothing to install before you begin. Your count and your history live inside this browser only, under the counter's own storage key, so the page on day one behaves the same way it will on day thirty — except that previous days now show up in the history panel. This walkthrough covers a first run from the moment the page loads to the moment you have at least one saved day in your history and, if you want one, an exported file sitting on your own device.
What the Tasbih Counter Does at a Glance
By design, the Tasbih Counter page has one job: count your entries against a chosen round target and keep a daily record you can review later. It is not a religious reference, a recitation library, or a tool that prescribes how many counts belong in a given practice — those decisions stay with you. The surface shows three values together: your chosen target, the round number you are currently inside, and your position inside that round, updated on each tap. Because state stays in this browser, you can refresh, switch tabs, walk away, and come back later; the count on today's date remains where you left it.
Two settings are worth knowing before you tap anything: the round target, which can be 33 or 99, and an optional counter label you can write in plain text for your own reference. The label is local-only and is deliberately left out of any image export so a shareable PNG cannot reveal it. Everything else on the page is automatic. Aside from choosing your target and optionally naming the counter, the page needs nothing else from you. There is no theme picker, notification preference, or sync toggle to set on day one — those ideas do not apply to a page that stores state locally. The first time the page loads, the counter begins at zero with today's local date as the implicit bucket; from then on, every tap you make on the visible Add one button contributes to that day's entry in the history.
Set Up Your First Count
The first run does not take long. Follow the steps below and you will have a saved day in your history before the page is closed.
- Open the Tasbih Counter page in your current browser. The counter area reads "0 of 33" with the target defaulting to 33.
- Pick 33 or 99 by tapping the target selector. The main display updates immediately to show your new target.
- (Optional) Type a short label into the counter's name field. Use plain text intended for your own reference — the label stays local to this counter and never appears in image exports.
- Tap Add one once for each entry you want to record. The position number rises by one each tap. If you tap once too many, press Undo one to roll back the most recent tap.
- Watch for the visual completion state. When your position equals the chosen target, the page marks the round as completed; the very next tap moves to "1 of [target]" inside round two. For a target of 33, a count of 33 produces a closed round, and the following tap begins round two at "1 of 33."
- Leave the page open or close it; the day's count is saved to this browser as you tap.
Reading the Round, Position, and Target Indicators
The counter surface combines three numbers so you always know where you are: the current round, your position inside it, and the target you have chosen. If your target is 33 and the position reads "12 of 33," you are twelve entries into round one. The instant your position equals 33, the round closes and the visual completion state appears on the same surface — that is the boundary signal the page produces for you. The following tap starts the next round at "1 of 33," regardless of how long you pause in between, and the round counter advances by one.
An optional vibration is attempted at round boundaries on browsers that support Navigator.vibrate (see W3C Vibration API). Safari and certain locked-down browsers do not implement that interface, and any device with vibration disabled skips the cue entirely. The visual signal still fires in those cases, so the round boundary stays visible without it.
Reviewing the Local Daily History
Each saved increment is grouped by the device's local calendar date, not by UTC. The detail matters for late-night work — if you keep counting across midnight on your phone, the entries from before midnight remain attached to the day you actually counted them, instead of being silently reassigned to the new UTC date. When the local day rolls over, the visible page count starts back at zero, while earlier nonzero days remain listed in reverse date order inside the history panel.
The history panel stays intentionally modest: a date and the saved count for that date, with no profile, no inferred intent, and no aggregate chart. If you want a deeper walkthrough of what those numbers represent and how to confirm they match what you actually counted, the guide on checking results after using a tasbih counter covers verification step by step.
Exporting the Record as PNG or CSV
Once at least one day is saved, two export actions become available, and both run entirely inside this browser. The PNG export produces a 1080 by 1350 image with a Lizely mark, a total, and recent calendar-day rows; the optional custom label is intentionally omitted from the image so a shareable picture does not reveal any personal note you typed. The CSV export produces a simple two-column file — Date on the left, Count on the right — with one data row per saved nonzero day. There are no formulas or hidden summaries; pasting the file into a spreadsheet lets you apply your own totals or charts without first parsing anything. You can keep the CSV as a private archive on your device or delete it whenever it is no longer useful. Neither action uploads your data to a server; the page uses native canvas and Blob interfaces to build the file locally and then hands you the download.
An export is not the same thing as a backup. Because state lives only in this browser's localStorage — defined by the WHATWG HTML Web Storage specification — the PNG or CSV you download is the only place your data ends up outside this page. Clearing browser data, opening a private window, or switching to another device starts a fresh empty counter on that other surface; counts from the original device stay where they were saved.
| Aspect | PNG export | CSV export |
|---|---|---|
| Output type | 1080 by 1350 image | Two-column text file |
| Visible content | Lizely mark, total, recent calendar-day rows | Date and Count columns with one row per saved day |
| Includes the optional label | No — label is omitted on purpose | No — the label is not a saved field |
| Typical use | Sharing a visual summary or saving as an image | Spreadsheet work, archiving, or replaying in another tool |
| Where it is built | Native canvas inside this browser | Native Blob download inside this browser |
Choosing Between the 33 and 99 Targets
Both targets follow the same boundary rule — the visual completion state appears at the exact number you selected — but a shorter round and a longer round produce different rhythms on the surface. The table below spells out the practical difference so you can pick a default before you start counting.
| Aspect | 33 target | 99 target |
|---|---|---|
| Round length | A round closes at 33 entries | A round closes at 99 entries |
| Boundary behavior | Visual completion state appears at exactly 33 | Visual completion state appears at exactly 99 |
| After a round closes | Next tap starts round two at "1 of 33" | Next tap starts round two at "1 of 99" |
| Switching later | Target can be changed for the next interaction | Target can be changed for the next interaction |
| Optional label | Local only; omitted from PNG export | Local only; omitted from PNG export |
When the Tasbih Counter Is the Right Tool
The page fits the case where you need a private, repeated count against a fixed 33 or 99 round boundary with a small daily record you control. The scope stays deliberately small: the tool makes almost no decisions for you beyond the target and the round marker. If instead you want an adjustable step size and a general repeated-event label with the same kind of local export, the Online Tally Counter is the better fit. If each completion is a workout set with repetitions and an optional rest timer, a Workout Rep Counter matches that workflow more directly. Choosing between them rarely requires a long decision; the smallest tool that matches your real workflow is usually the one that stays in your bookmarks.
Related reading: Fix Wrong Results After Using a Water Intake Counter.