Google Tasks: the complete guide [2026]

Google Tasks is the to-do list built into every Google account. It runs inside Gmail's sidebar, the Google Calendar side panel, a standalone web app at tasks.google.com, and a mobile app for iOS and Android. The product is free, ships with both personal Gmail and Google Workspace accounts, and supports lists, due dates with times, deadlines, one level of subtasks, recurring tasks, Google Drive attachments, and a tight connection to Google Calendar. It does not support task priority, labels, native list sharing, assignees, rich-text notes, or multi-level subtask nesting.

What is Google Tasks?

Google Tasks is the default task manager bundled with every Google account, both personal Gmail and Workspace. The data lives in the same Google account as your Drive, Calendar, and Contacts, billed and secured under the same umbrella, with no separate signup.

Tasks runs in four places, and they are all the same list under the hood:

• Gmail sidebar on the web. Click the blue checkmark icon on the right rail to open the panel.
• Google Calendar side panel on the web. Same icon, same panel, same lists.
• The standalone web app at tasks.google.com. A full-page view of the same data.
• The mobile app for iOS and Android. Capture from your phone, sync to everything above.

Whatever you create in one surface appears in the others on the next sync. There is no separate "Tasks workspace" to switch between, and no premium tier to upgrade to. Google Tasks is the default to-do list bundled with every Google account, accessible from Gmail, Calendar, the web, and mobile.

The basics: capture, complete, lists

The core loop in Google Tasks is three actions: capture a task, organize it on a list, and check it off when done. Once you know where to click for each, you have the full product.

• Capture. Click the Tasks icon in any of the four surfaces above, hit Add a task, type a title, and optionally add details or a date and time. Press Enter to save. On mobile, the floating + button does the same. Once a task exists, the three-dot menu on each row exposes four actions: Add deadline (a date-only marker, separate from a timed due date), Add a subtask, Add attachment (a file from Google Drive), and Delete.
• Lists. Tasks groups everything into lists. The default list is My Tasks; create more from the dropdown at the top of the panel (Create new list). Use one list per context: Work, Personal, Reading list, Errands. You can drag tasks between lists from the standalone web app.
• Complete. Click the empty circle to the left of any task to mark it done. Completed tasks collapse under a Completed header at the bottom of the list, with a count next to it. To un-complete a task, expand the section and click the filled circle again.

Recurring tasks

Recurring tasks are the area where Google Tasks behaves differently from most to-do apps, and the difference matters. The setup is short: click a task in the list to open its detail panel, give it a date and time, then click Repeat and pick Daily, Weekly, Monthly, Yearly, or Custom for an arbitrary interval. The recurrence saves as soon as you close the panel, and the next occurrence shows up on the chosen schedule.

The quirk: Google Tasks stores one task with a moving due date. It does not create a new task per occurrence. When you complete this Monday's "Weekly review," the same task's date advances to next Monday. There is no per-occurrence history, no log of "did I do this 4 weeks in a row," and no way to skip a single instance without skipping the whole pattern.

For most people this is fine. The current occurrence is what you need to act on, and the date advances reliably. For anyone tracking habit consistency or recurring deliverables across weeks, the missing history is real, which is why people who care about streaks typically reach for a dedicated habit tracker app or a Notion habit tracker template instead of trying to bend Google Tasks into one.

Google Tasks recurring tasks store one task with a moving due date; completing advances the date rather than creating a new task. If you need per-occurrence rows, mirror the task to a Notion database where each completion can become its own page.

Subtasks and list structure

Tasks supports subtasks one level deep and no further. Add a subtask by pressing Tab after a task, or use the menu (three dots) → Add a subtask, or drag a task slightly to the right to indent it. The subtask appears indented under its parent and inherits nothing automatically (no due date, no notes); it is a free row that happens to be tied to a parent.

The hard rule: subtasks cannot have their own subtasks. Try to indent a subtask further and the UI does nothing. The limit is enforced by the Google Tasks API, not a UI choice, which means no Chrome extension, no third-party app, and no future Google update is likely to add depth without breaking the API contract. Google Tasks supports one level of subtask nesting. Subtasks cannot have their own subtasks.

If you need deeper structure (project → phase → task → subtask → checklist item), Google Tasks is not the tool. The two practical workarounds:

• Use a separate list per project phase, treating list names as the second level of nesting.
• Mirror tasks to Notion via a two-way sync, where the same parent-task relation can extend to any depth via Notion's own relation property.

Tasks in Google Calendar

Any Google Task with a date and a time appears on your Google Calendar grid as a time-blocked entry, color-distinguished from regular events (typically a lighter shade with a checkmark icon). Drag it on the grid to reschedule, and the new time syncs back to Tasks on the next cycle.

The Tasks side panel inside Calendar mirrors the Gmail sidebar exactly: the same lists, the same capture loop, the same recurrence options. If you live in Calendar all day, you do not need to leave it to manage tasks. Google Tasks with a time appear in Google Calendar as time-blocked entries you can drag to reschedule.

For the deeper Tasks-plus-Calendar workflow (multi-list views, scheduling subtasks, blocking deep work, routing both into a single Notion view), see how to sync Notion with Google Calendar for the calendar-side pairing.

Mobile and the iPhone widget

The Google Tasks mobile app for iOS and Android carries the same capture loop in a smaller surface. The two questions readers actually ask are how to install it and how to get a useful widget on the home screen.

• Install. Download Google Tasks from the App Store or Play Store. Sign in with the same Google account you use on the web, and your lists appear on the first launch. There is no separate Tasks account.
• iPhone widget. Long-press an empty area of the home screen until the icons jiggle, tap the + in the top-left corner, search Tasks, and pick the small or medium widget. The widget shows tasks from a single list at a time; tap the widget to switch lists in the app.
• Android widget. Long-press the home screen → Widgets → scroll to Tasks → drag the widget onto the home screen. Android exposes a slightly larger widget surface than iOS but the per-list limit is the same.

The honest limit: the iPhone widget shows one task list at a time; combining lists into a single widget view is not supported. If you keep separate Work and Personal lists, you keep separate widgets, or you collapse them into one list and lose the separation. Most users settle on a single mixed list on mobile and let context filters do the work on desktop. If those lists are already mirrored to a Notion database, the Notion mobile app gives you a single filtered view across all of them, and the widget constraint stops mattering.

Sharing workarounds

Google Tasks has no native sharing. You cannot share a list, assign a task to a teammate from inside Tasks, or see another user's tasks even within the same Workspace. The product is built as a personal tool and Google has not extended it in this direction.

The three workarounds that exist:

1. Assign via Google Chat spaces. Inside a Chat space, click the Tasks tab → Add space task → assign to a member. The task appears in that member's Google Tasks list, with the Chat space name as the list. This is the only mechanism Google supports for one-person-to-another task assignment, and it requires a Chat space, not just direct message threads.
2. Mirror a list to a shared Notion database. Each teammate connects their own Google Tasks list to a shared Notion database via a two-way sync; the team sees everyone's tasks side by side, filtered and grouped however the Notion view dictates. The advantage over Chat-based assignment is that it does not require the assigner to be in Chat at all; the Notion view is the surface.
3. A single shared Google account. Multiple users log into the same Google account with shared credentials. Mentioned for completeness; this is not recommended (audit trail collapses, password rotation becomes painful, every change looks like it came from one person).

What Google Tasks can't do

Reading a Tasks guide that only covers the capabilities is reading half the picture. The limits are short, real, and the same in every surface.

• No task priority. No P1/P2/P3, no high/medium/low, no star or flag. The only sort order is creation order or due date. Workaround: prefix titles with [P1], or maintain priority in Notion via field mapping.
• No labels or tags. No @home, @office, #errand. The closest substitute is separate lists, which act as a poor man's label.
• No assignees on personal tasks. Assignment exists only inside Chat spaces (above), not on tasks you create in your own lists.
• No native list sharing. Covered in the sharing section.
• Notes are plain text only. No formatting, no checklists inside the note, no images. Attachments are supported via the per-task menu but they live alongside the note, not inside it; the note field itself stays plain text.
• One level of subtask nesting. Covered in the subtasks section.
• No project view, no Kanban, no Gantt. Tasks is a list, not a project manager. If you need any of those, you are looking at a different category of product.

Google Tasks does not support priority levels, labels, native list sharing, rich-text notes, or multi-level subtask nesting.

If most of these gaps matter to you, the choice is between switching tools entirely (see Todoist vs Google Tasks for the most common upgrade path, or the broader best to-do list apps and best planner apps roundups for the wider field) or layering Notion on top of Google Tasks so each app does what it does best. The next section covers the second option.

Bringing Google Tasks into Notion

Google Tasks captures fast. Notion organizes deep. The combination is what most Notion users converge on once they hit the Google Tasks limits in the previous section: Tasks stays as the fast capture surface, and Notion absorbs the structure layer Google Tasks does not ship with.

Mirroring your tasks to a Notion database is what makes that combination work. It unlocks:

• Priority as a Notion Select property, since Google Tasks has none.
• Labels and tags as a Notion Multi-select.
• Project relations linking each task to a project page, a client record, or a meeting note.
• Custom views (board, calendar, timeline, gallery) over the same underlying tasks.
• Rollups and formulas that work across the whole database, so a parent project page can show its task count, completion rate, and the nearest deadline automatically.
• A second-brain hub where tasks live alongside the projects, notes, and contacts they belong to, instead of in a sidebar disconnected from everything else.

Notion has no native Google Tasks integration, so the connection runs through a third-party sync layer. 2sync connects a Google account to a Notion database and keeps changes flowing both ways. A task captured on your phone lands in a row of your Notion database within minutes; a deadline moved in Notion updates the task in Google Tasks on the next cycle. The same applies to completions, subtasks, and edits.

The 2sync wizard exposes 15 fields in total. Each one accepts one or more compatible Notion property types, for example, Task Title can map to a Title, Text, or Select property; Completed can map to a Checkbox or a Status. Most of the core data fields sync two-way; the metadata fields that 2sync writes into Notion are one-way (Google Tasks owns the value); a single control field runs the other direction so you can delete a Google Task by toggling a Notion property.

Core Google Tasks fields:

Metadata and control fields the wizard adds:

The metadata fields are optional and ship (Not set) by default, turn them on only if you want the extra context inside Notion (which automation a task came from, where it sits in the list, the link back to tasks.google.com, the internal Task ID). Trigger deletion on Google Tasks is the one inbound field: when the Notion property you map evaluates true (Checkbox checked, Status set to the trigger value, Formula or Rollup matches), 2sync deletes the task in Google Tasks on the next cycle.

Full per-field behavior, the rich-text-to-plain-text conversion on Description, the recurring-task handling, and the parent-task relation semantics all live in the Google Tasks field reference.

A creative consultant in Los Angeles, Rob Feng, runs a solo consultancy on Notion as a second brain. Before 2sync, his Google Tasks lived parallel to his Notion project databases with no connection. After connecting them, his tasks captured on phone or laptop land in Notion next to the project they belong to.

If you also keep tasks in Todoist alongside Google Tasks, the same 2sync setup connects both into one Notion database, with each task tagged by its source app. If your day already runs in Google Calendar, the calendar-side guide shows how events and tasks land in the same Notion view.

Example of our Google Tasks already synced into Notion through 2sync.

##Final thoughts

Google Tasks is the right tool for one job: fast capture into a flat list, with a tight tie to Gmail and Google Calendar. Its limits cap it as a standalone manager: no priority, no labels, no native sharing, no project view. Within its job it is dependable, free, and built into surfaces you already use every day.

The pragmatic stack for most Notion users is to keep Google Tasks as the capture layer and let Notion carry the structure. Each app does the work it does best, and a two-way sync keeps them aligned without manual copy-paste.

FAQ