A satisfactory to-do list is one that turns vague intentions into observable next actions you can mark complete. To use a browser-based checklist like To-Do List, type one task at a time into the New task field, then select Add or press Enter to place it in the list. A checkbox sits next to each row so you can move it between active and completed states without removing it. The summary keeps both totals visible: how many items exist and how many are checked off. When a session ends, Clear completed sweeps finished entries while leaving active work intact, and the per-item Delete control removes a single line. Everything lives in the versioned localStorage of the current browser profile, so the list survives a page reload without an account, an upload, or a network connection. The interface stays small on purpose: the New task input, the list, the per-row checkbox, the Delete control, and the Clear completed button are the only controls, which keeps the cognitive load low enough that a satisfying run-through of a few items at the end of the day is genuinely possible.
Add your first task and see it stay put
The fastest path to a satisfying list is a single concrete first task. The To-Do List page is intentionally small, so setup takes less than a minute and there is no sign-in to slow you down. After the page loads, it waits for the versioned localStorage record to be read before turning the input on, which keeps a fresh empty React state from overwriting any tasks that were already saved on a return visit. Once that loading boundary passes, every action you take replaces the stored JSON with the validated version of the list.
Follow these steps to go from a blank tab to a working list:
- Open the To-Do List in the browser tab where you usually work.
- Click into the New task field and write one concrete task. Keep it under 160 characters, and avoid leading or trailing whitespace, because an all-whitespace entry is rejected on Add.
- Select Add, or press Enter while the field has focus, to drop the row into the list. Each new item receives a browser-generated UUID so React keeps stable list identity through later edits.
- Find the new row with its checkbox on the left for completion status and a separate Delete control on the right for that line alone.
- Use the checkbox to move a task between active and completed without changing the wording. Marking complete is the only state change here; the text never edits itself.
- Reload the page once and confirm the row is still there. A successful reload is your proof that the list lives in localStorage rather than only in memory.
- Use Clear completed to wipe finished entries in one pass when the day's work is done, or choose Delete on a single row to remove a line you no longer need.
Three controls, three jobs
The interface stays focused by giving each operation a single, unmistakable control. That separation is what makes a checklist satisfying to use: nothing happens by accident, and there is no hidden menu to discover. The table below pairs each control with the moment in a session where it tends to fit best.
| Control | What it does | Best moment to reach for it |
|---|---|---|
| Checkbox beside a row | Toggles the task between active and completed without removing the text | When the stated result of the task now exists |
| Delete on a single row | Removes only that entry, immediately, with no undo | When you no longer want the task in scope at all |
| Clear completed | Removes every completed entry at once while leaving active work intact | At the end of a session, when you want a quieter view for tomorrow |
The Clear completed control is disabled while no items are finished, which prevents an accidental click from changing a list that nothing could usefully change. The Delete control, by contrast, always works on its own row, and the change is intentionally immediate. Because neither action keeps history, treat both as final and copy wording elsewhere if you may need an audit trail later.
Write each line as a next observable action
A to-do list is most satisfying when each line describes a result you can verify at a glance. The product is built around the idea that broad goals stall while concrete next actions move. Replace "Proposal" with "Send the revised proposal to legal," and you turn a wish into a single observable step. Replace "Photos" with "Back up phone photos to the external drive," and you turn a worry into a chore that takes a known amount of time and ends in a known state. If you want a fuller daily routine around observable lines, the guide on how to use a to-do list effectively every day goes deeper on shaping the day around a short list.
Mark complete only when the stated result exists. If a task says "Send the revised proposal," the row should stay active until the proposal has actually gone out — not when it is drafted, not when it is saved on a local drive, but when it has been delivered. This small rule is what makes the completed counter meaningful at the top of the list and what makes a quiet Clear completed feel like progress instead of cleanup. If you want a useful end-of-day pass, work top to bottom: read each active line, ask whether the stated result now exists, and check only those where it does.
The practical limits before you start
Even a simple checklist has bounds, and knowing them keeps the interface fast and predictable. The product contract defines the exact values below.
| Limit or input rule | Exact value or behavior |
|---|---|
| Maximum tasks in the list | 100 concise entries |
| Maximum characters per task | 160 characters |
| Whitespace handling | Leading and trailing whitespace removed on Add; all-whitespace entries are rejected |
| Identifier per task | Browser-generated UUID for stable editing |
| Storage location | localStorage under a versioned key in the current browser profile |
| Corrupt-data handling | Malformed JSON, duplicate IDs, invalid completion values, oversized tasks, and over-cap lists are rejected as a unit instead of being rendered |
The 100-task ceiling is deliberate. A bounded list keeps local restoration quick, keeps the page interface focused, and prevents the tool from being used as an unbounded document store. When a project grows past that point, the right answer is to move the long-lived work into a dedicated task manager rather than to push the list past its design.
Local storage is private, but not absolute
"It stays in your browser" means exactly what it says, with one important boundary. The list is stored in localStorage under a versioned key tied to this site's current browser profile, and it is not attached to a Lizely account, not synchronized between devices, not shared between browsers, profiles, or private windows, and not uploaded to any server. Anyone who can use the same unlocked browser profile on the same machine may be able to read the list. Browser extensions and device administrators may also have access to page storage. Because the tool is a convenience rather than a backup system, keep important deadlines and irreplaceable project records in a dedicated task manager or another backed-up service. Clearing site data, resetting the browser profile, or running a cleanup utility will remove the stored list. For a workflow that needs to survive those events, copy critical wording elsewhere before deleting or clearing.
Privacy is local, but the list is not encrypted. Do not store passwords, recovery codes, medical records, financial account details, or other secrets. The tool's small scope is a feature: it is a private, lightweight checklist, not a vault or a shared productivity system. If you treat it that way, every reload is a fresh, predictable starting point.
When a lightweight checklist stops being enough
A browser list feels satisfying as long as the work fits on one screen, on one device, with one person. The moment a deadline belongs to a group, the moment a task has to fire at a specific hour, or the moment a line needs to recur weekly, the tool's scope ends and a fuller system should take over. The product deliberately omits dates, reminders, priorities, collaboration, recurring work, subtasks, and cloud synchronization because those features need notification permissions, account identity, conflict handling, or a larger data model than a 100-entry local list can carry. The narrower scope is what keeps the page fast, the interface understandable, and the localStorage record bounded.
Use the To-Do List for a temporary personal checklist, a short shopping list, a packing pass, or a small set of steps you are completing at one workstation, and reach for a full task manager the moment another person has to see updates, or missing a deadline would cause real harm. For everything in between — the daily mix of small next actions that fits on one screen — the three controls described above and the rules in this article are usually enough to leave you satisfied at the end of the session.