The fastest path to a Microsoft to-do list when Microsoft To Do feels too heavy is a single browser tab that stores your tasks locally, marks them complete with a checkbox, and removes finished entries with a Clear completed button — no Microsoft account, no sync between devices, and no extra app to learn. Microsoft's own To Do is the heavier option, built into Outlook with due dates, reminders, steps, shared lists, and cross-device sync, but every entry round-trips through your Microsoft account. A lighter alternative lives in a private browser profile: you type a task, press Enter, and the entry stays put until you delete it or clear the completed items together. This article walks through the practical setup, the exact controls you get, the privacy boundary that makes it safe for casual use, and the moments when it makes sense to step up to Microsoft To Do or a dedicated task manager instead. The keyword itself leaves room for three interpretations — Microsoft To Do the cloud app, a checklist inside Outlook, or a personal list you happen to open while working inside Microsoft 365 — and each interpretation has a different setup path. Knowing which one fits is the first decision, and the local browser option is often the right call for one-off work.
Three ways to set up a to-do list in Microsoft
Searching for a to-do list inside Microsoft usually surfaces Microsoft To Do first, because it ships with Windows and is pinned inside Outlook on the web. Microsoft To Do is a full task management app: it supports due dates, reminders, recurring tasks, steps, file attachments, shared lists, and cross-device sync through your Microsoft account. If you already live inside Outlook and need those features, Microsoft To Do is the natural choice and the official answer to the search query.
The second option is a lightweight checklist inside Outlook itself, accessed through the My Day pane or the Tasks module. It accepts quick entries, surfaces upcoming calendar items, and ties tasks to flags in your inbox. It still requires a Microsoft account and stays tied to the Outlook client, so it is heavier than the third option and lighter than the full To Do app.
The third option is a single browser tab that behaves like a paper checklist on screen. The To-Do List page shows an input field, a list of tasks, and three controls — a checkbox, a delete button, and a Clear completed button — without any account, sync, or server connection. That last option is the focus of the rest of this article, and it is the right pick for short, solo, single-device work where a Microsoft account feels like friction.
| Feature | Microsoft To Do | Outlook checklist | Local browser list |
|---|---|---|---|
| Account needed | Microsoft account | Microsoft account | None |
| Sync across devices | Yes | Yes (within Outlook) | No |
| Due dates and reminders | Yes | Yes | No |
| Steps or subtasks | Yes | No | No |
| Shared list | Yes | Limited | No |
| Maximum entries | Unlimited | Unlimited | 100 |
| Where data lives | Microsoft cloud | Microsoft cloud | Browser localStorage |
The table shows the boundary clearly: Microsoft To Do is a cloud productivity system, the Outlook checklist is a trimmed view of the same system, and a local browser list is a temporary private scratchpad. Each tool has a job it does better than the other two, and that job sets the trigger for switching between them.
Set up a quick browser-based to-do list
The path of least resistance when you want a Microsoft to-do list without signing in is the To-Do List page. Everything you add lives in that browser profile and nothing is sent to a server, which is the same shortcut many people use for a packing list, a short shopping list, or a single-day work sprint. Follow the steps below to get from a blank tab to a working list.
- Open the To-Do List page in your browser and wait for the input field to activate. The list disables itself briefly while it reads the previous session from storage, so any existing tasks reappear before you can edit and the empty state cannot overwrite saved data.
- Click the New task field, type one concrete task — for example "Send the revised proposal" rather than just "Proposal" — and select Add or press Enter. Leading and trailing spaces are stripped automatically, an entry that contains only whitespace is rejected, and each task can hold up to 160 characters.
- Repeat to keep adding tasks. Every new entry receives a browser-generated identifier so it stays stable for the checkbox and delete controls even after reorders or reloads.
- Use the checkbox beside any task to switch it between active and completed. The summary near the top of the page updates to show the total number of tasks and how many you have already finished.
- Reload the page to confirm local persistence. The same list should reappear in the same order; if it does, the browser profile is keeping the data exactly where the previous session left it.
- Delete a single task with the control beside it when you want it gone for good, or use Clear completed to remove every finished entry together. Clear completed stays disabled when nothing is complete, which protects you from no-op clicks.
That is the entire workflow: add, tick, reload, delete or clear. Three visible controls, one text field, and zero accounts to remember.
Write each line as the next physical action
A to-do list works when each line is the next observable action, not the project it belongs to. The product supports this directly because every entry is plain text capped at 160 characters, with whitespace trimmed and empty entries rejected, so there is no temptation to dump a paragraph in and call it a task. Mark the item complete only when the stated result exists, not when you have moved some intermediate step forward.
- "Proposal" — too broad, never finishes as written because there is no stated state.
- "Send the revised proposal" — a single, checkable action that ends when the email leaves your outbox.
- "Photos" — vague, will sit on the list for weeks as a low-grade reminder.
- "Back up photos to the external drive" — done in one sitting once the copy finishes and you eject the drive.
Action-shaped tasks also keep the 100-entry ceiling usable. The cap is intentional: it prevents the page from quietly turning into an unbounded note file, and it keeps the interface focused. A focused sixty-item sprint is a healthier checklist than a thousand-line brain dump, and the cap nudges you to copy long projects elsewhere.
Where the list lives — and where it doesn't
All entries are stored in localStorage under a versioned key inside the current browser profile. They are not attached to a Lizely account, not synchronized between devices, browsers, private windows, or profiles, and not uploaded to the site's server. If you open the same page in another browser, you will see an empty list — that separation is the feature, not a bug, and the tool is built from the start as a single-device scratchpad.
The same constraint means clearing site data, resetting the browser profile, or running a cleanup utility can remove the list without warning. Reloading restores a valid stored list on the same profile, but malformed entries, duplicate identifiers, invalid completion values, oversized tasks, and lists beyond the supported limit are rejected as a unit, so the page never renders untrusted data even if something else wrote bad JSON to that key. localStorage is a convenience rather than a backup, so anything you cannot afford to lose belongs in Microsoft To Do, OneDrive, or another backed-up system. For a fuller walk-through of how browser-side persistence works day to day, see how to keep track of a to-do list in your browser.
When a real task manager is the right tool
The local list is the right tool when the work is short, solo, and fully under your control on one device. It is the wrong tool the moment another person needs to see the list, a reminder must fire at a specific time, or a missed deadline costs real money. Microsoft To Do, Microsoft Planner, or a dedicated app like Things or Todoist are designed for those jobs and they handle dates, recurrence, shared lists, and notifications that this page deliberately leaves out on purpose.
Because the tool stores tasks in plain text under a versioned localStorage key and does not encrypt them, it should not be used for passwords, recovery codes, medical notes, or financial account details. Use a password manager for credentials, a notes app with a backup for medical records, and a bank statement download for finances. Anyone who can use the same unlocked browser profile may be able to read the list, and browser extensions or device administrators may also have access to page storage.
Privacy and limits of a local checklist
Local does not mean secret. The data only stays on the device profile that wrote it, but it is unencrypted, and a second person with the same unlocked browser session can read every line. The boundary the tool actually provides is narrower than a password vault and wider than a cloud-synced productivity suite. That trade-off is fine for packing lists, single-day work blocks, and shopping runs. It is not appropriate for anything that needs to stay confidential against an attacker who already shares the device or a curious visitor who can open the browser.
The tool also avoids a defined set of features on purpose. There are no due dates, no reminders, no priorities, no collaboration, no recurring tasks, no subtasks, and no cloud synchronization. Those features need notification permissions, account identity, conflict handling, or a larger data model. Skipping them is what keeps the page fast, focused, and understandable after a single read. Pick another tool the day any of those features become non-negotiable — keeping a one-week checklist in this page is fine, but running a product roadmap through it is a recipe for missed work and unrecoverable deletions.