A browser-based to-do list keeps up to 100 tasks stored locally on the device you are using right now, marks each item complete with a single checkbox click, and works without an Outlook account, an email sign-in, or any software install. Outlook's built-in To Do feature does more than that — it syncs across devices, supports due dates and reminders, and connects with Microsoft 365 calendars — but it also requires a Microsoft account, the new Outlook client, or an active internet connection. For someone who only wants a fast personal checklist they can open on one workstation, the browser tool covers the same three core actions (add, complete, and delete) without the setup. Tasks live in localStorage under a versioned key, deletions are immediate with no undo history, and every entry is capped at 160 characters to keep the list focused on next actions rather than long notes. This guide walks through how the two options compare, how the browser list stays put between page reloads, and exactly how to add, complete, and clear tasks so nothing slips between sessions.
Use the To Do List Inside Outlook
Microsoft's To Do is the official task surface inside Outlook. In the new Outlook client and on Outlook.com, the To Do pane shows the lists you create plus a daily "My Day" view that combines upcoming calendar items with your active tasks. You can open the To Do pane from the navigation, type into the "Add a task" field, pick a list from the sidebar, and press Enter to commit the entry. In classic Outlook, the To Do bar on the right side of the window surfaces calendar events, flagged email, tasks, and contacts in a single column, and you can drag a message or a contact onto that bar to convert it into a tracked task. Tasks created this way sync through your Microsoft account, show up in the dedicated To Do app on other devices, and support due dates, recurring schedules, file attachments, and shared lists with other Microsoft 365 users.
The trade-off is the surrounding surface area: To Do in Outlook is built for people who already live inside a Microsoft 365 account and accept the sign-in, the sync, and the optional client install. Anyone without that account, anyone who cannot install the new Outlook client on a particular machine, or anyone who simply wants a faster path to a checkbox list will hit friction that has nothing to do with the actual task tracking. For the full step-by-step on the Microsoft path, see the full step-by-step guide to the To Do list in new Outlook; the rest of this article focuses on the simpler browser alternative.
Use a To-Do List in Your Browser Instead
The browser To-Do List is a focused alternative that drops the account requirement, the calendar hooks, and the shared list model. It runs entirely in the current browser, saves up to 100 tasks in localStorage, and stays private because nothing is uploaded to a server. Here is the exact sequence to get a first task on the page and keep it there across visits.
- Open the To-Do List page in the browser profile where you want the tasks to live.
- Click into the New task field and type one observable next action (for example, "Send the revised proposal to finance" rather than "Proposal").
- Select Add to add the task, or simply press Enter while the field is focused — both do the same thing. Leading and trailing whitespace is trimmed automatically, and an entry that is empty after trimming is rejected so blank rows never appear.
- Use the checkbox beside a task to switch it between active and completed. The summary line updates the total count and the completed count the instant you click.
- Reload the page to confirm local persistence — your tasks come back from localStorage as soon as the page finishes loading, so a closed tab or a refresh never costs you a list.
- Select the Delete control on a single task to remove just that item, or select Clear completed to remove every finished task at once. Clear completed is disabled when nothing is finished, which removes the chance of an accidental click that would have no useful effect.
The interface deliberately omits dates, reminders, priorities, recurring schedules, subtasks, and cloud sync. Those features need account identity, notification permissions, or a richer data model, and adding them would push the tool out of the "open the page and start typing" zone that makes it useful.
Outlook's To Do vs. a Browser Checklist Side by Side
The table below compares the two surfaces on the dimensions a person searching "how to use to do list in outlook" typically weighs before picking one. Where a value is set by the Lizely product contract it is taken verbatim from that contract; values for Outlook's To Do describe the publicly documented behaviour without claiming a verified test.
| Capability | Outlook's To Do (new Outlook, Outlook.com, To Do app) | Browser To-Do List |
|---|---|---|
| Microsoft account required | Yes | No |
| Cross-device sync | Yes, through Microsoft cloud | No, single browser profile only |
| Due dates and reminders | Yes | No, not supported |
| Calendar integration | Yes, ties into Outlook calendar | No |
| Sharing and collaboration | Yes, shared lists are supported | No |
| Max number of tasks | Not formally capped in published docs | 100 tasks |
| Max characters per task | Not formally capped in published docs | 160 characters |
| Storage location | Microsoft cloud servers | localStorage in the current browser |
| Works offline | Limited, depends on the client | Yes for the current browser session |
| Typical setup time | Several minutes (sign-in, sync, optional install) | Under a minute |
If your work needs reminders, shared ownership, or cross-device presence, Outlook's To Do is the right tool. If you want a focused, private, single-workstation checklist that requires no sign-in, the browser surface gives you the same add/check/delete core in a smaller package.
How Tasks Survive a Page Reload
The browser To-Do List saves tasks in localStorage under a versioned key that belongs to the current browser profile. The page waits until that storage record is read before the interactive list is enabled, which prevents the initial empty React state from overwriting your existing tasks during startup. After loading, every add, checkbox toggle, delete, or Clear completed action rewrites the stored JSON with the current validated list. As a safety boundary, malformed JSON, duplicate identifiers, invalid completion values, oversized tasks, or lists beyond the 100-task cap are rejected as a unit rather than rendered as trusted interface data, which keeps a corrupted entry from breaking the rest of the page.
This model has practical limits. The list will not appear on another device, in another browser, in a private window, or in a separate browser profile — each one keeps its own store. Clearing site data, resetting the browser profile, or running a cleanup utility removes the list, so localStorage is a convenience rather than a backup system. Important deadlines, project records, or anything a colleague might need should live in a backed-up task manager. For a personal checklist that lives on one workstation, the versioned localStorage record is enough to carry a list across tabs, refreshes, and short breaks.
Write Tasks as Observable Next Actions
A short list works best when each entry is something you can mark complete in a single sitting. "Proposal" is too broad — you cannot tick it off until the entire proposal is finished, and the open-ended label invites procrastination. "Send the revised proposal to finance" is an observable next action: you know what "done" looks like (an email sent), and you can check the box the moment that result exists. The same pattern works for personal tasks: "Back up phone photos to the external drive" is checkable; "Photos" is not.
The browser tool helps enforce that habit. Every entry is trimmed of leading and trailing whitespace when you add it, an all-whitespace entry is rejected, and the 160-character per-task cap stops long descriptions from sneaking onto the list. The 100-task cap acts as a second boundary: when the list starts feeling crowded, that is a signal to clear completed items, archive finished work elsewhere, or move the project into a fuller task manager. A simple rule of thumb — write the task the way you would tell a teammate to do it — keeps the list short and the checkboxes honest.
Limits, Privacy, and When to Move Back to Outlook
The browser To-Do List trades scope for speed. It deliberately omits dates, reminders, priorities, recurring work, subtasks, collaboration, and cloud synchronization because those features need notification permissions, account identity, conflict handling, or a larger data model. Anything missing from that list is missing on purpose: if a deadline matters, if someone else needs to see the same list, or if a missed reminder would cause real harm, switch back to Outlook's To Do or a dedicated task manager.
Privacy is local but not absolute. The list does not upload tasks, so the entries do not leave the current browser profile — but anyone who can use that unlocked profile on the same machine may be able to read the list, and browser extensions or device administrators can sometimes reach page storage. The tool does not encrypt entries; it simply avoids sending them to a server. Do not store passwords, recovery codes, medical records, financial account numbers, or other secrets.
Deletion is immediate and irreversible on both Delete and Clear completed. There is no undo history and no recycle bin. If you may want an audit trail, copy the task wording elsewhere before removing it. The cleared view is quieter, but it is also permanent, so treat Clear completed like the final step of a session rather than a routine cleanup that you can reverse later.
For a deeper look, see Outlook 365 To-Do List: Native Tools and a Browser Option.