What is Keyboard Shortcut for a Tick? Inserting a Checkmark Efficiently

Learn practical keyboard shortcuts to insert a checkmark (tick) across Windows, macOS, and Linux. This guide covers Alt codes, Unicode input, and clipboard methods with reliability tips.

Shortcuts Lib Team

February 8, 2026·5 min read

Keyboard Shortcuts Windows Shortcuts Copy Paste Mac Shortcuts

Tick Shortcuts - Shortcuts Lib — Photo by RaniRamlivia Pixabay

Quick AnswerDefinition

Short answer: there is no universal single key combination for a tick. Methods vary by OS and app. Common options include Windows Alt+2713, Linux Unicode input (Ctrl+Shift+U 2713), macOS Unicode Hex Input (Option+2713), or simply copying and pasting a ✓. This article shows how to use these approaches reliably.

Quick Primer: what is a tick and why it matters in tech writing

In the world of documentation and everyday tech tasks, a tick (checkmark) communicates completion, verification, or agreement. If you’re asking what is keyboard shortcut for a tick, the answer depends on your operating system and the application you’re using. In this guide, we explore practical shortcuts across Windows, macOS, and Linux, and we show you reliable alternatives like copy-paste when a glyph isn’t available in your font. Below you’ll see real, working examples you can adapt to your workflow.

Bash

# Quick test: print a checkmark to a log file
echo "Task complete ✓" >> audit.log

This approach is handy for auditors and engineers who generate logs or docs that must show a completed state. Using a checkmark in your messages reduces ambiguity and helps readers scan for status indicators quickly.

OS-specific methods to insert a tick

Different environments expose different key sequences or input methods. The most portable approach is Unicode input, but many users still rely on Alt codes or clipboard methods. We summarize three practical paths:

Windows: Alt+2713 is the classic way to produce a checkmark in many editors when Num Lock is active.
Linux/Unix: Ctrl+Shift+U 2713 Enter (Unicode input) works in many editors and terminals.
macOS: Unicode Hex Input (Option+2713 after enabling the input source) inserts a checkmark directly in editors that support UTF-8.

PowerShell

# Windows demonstration: print a checkmark to console (Unicode code point 2713)
Write-Output [char]0x2713

Bash

# Linux/macOS: Unicode input example (2713)
printf '\u2713\n'

Bash

# macOS (Unicode Hex Input) - text below describes the steps; actual typing is in the keyboard
# 1) Enable Unicode Hex Input
# 2) Switch to Unicode Hex Input
# 3) Type 2713 and press Return

Windows users often prefer the Alt code path, while Linux users lean on the Ctrl+Shift+U method, and macOS users rely on Unicode Hex Input. It’s also perfectly acceptable to copy a ✓ from a reliable source and paste it wherever needed. This reduces font compatibility concerns and ensures the symbol renders consistently across readers.

Tick insertion in common apps and editors

Different apps have their own quirks. Word processors generally support UTF-8 checkmarks; lightweight editors may fall back to the ASCII subset if the font omits the glyph. A practical pattern is to keep a tiny clipboard snippet of a checkmark and paste it as needed, or insert the glyph programmatically via a short script.

Python

# Python snippet to append a checkmark to a Markdown file
with open("notes.md","a",encoding="utf-8") as f:
    f.write("- [x] Task completed ✓\n")

Bash

# Append a checkmark to a text file (POSIX shell)
printf '\u2713\n' >> notes.txt

In Google Docs or Word Online, the simplest reliable path is to copy-paste the glyph from a trusted source. For developers embedding ticks in code comments or documentation, prefer a Unicode escape (\u2713) or a literal ✓ if UTF-8 is guaranteed. This prevents misinterpretation across locales and fonts.

Best practices and pitfalls

To maximize reliability, keep the glyph in a font that supports the character, and test across your target apps. If you’re distributing content widely, prefer using a text-based representation when possible (e.g., [x] for checked tasks in plain text), and reserve the actual glyph for finalized documents. Consider bundling a tiny helper snippet or macro you can reuse instead of retyping the sequence every time.

Bash

# Quick font check: verify that the glyph renders in your environment
if grep -q "✓" sample.txt; then
  echo "Checkmark renders correctly"
else
  echo "Font may lack the glyph; switch fonts or use ASCII fallback";
fi

Cross-platform consistency is the goal. When embedding in code or data, verify encoding (UTF-8) and the receiving platform’s font stack. This helps avoid surprises in downstream viewers or printers. Finally, document the method you choose in your style guide so teammates imitate it consistently.

Practical workflows and automation

Automating tick insertion can save time in CI pipelines, documentation generation, and task boards. For example, you can generate checklists with a script that appends a checkmark once a step is verified. The following snippet demonstrates how to generate a text snippet with a checkmark using a small Python script, which you can adapt for other languages or templates.

Python

# Generate a checklist line with a checkmark programmatically
checkline = "- [x] Complete integration tests ✓\n"
with open("checklist.md","a",encoding="utf-8") as f:
    f.write(checkline)

If you’re working in a terminal-based workflow, you can print a checkmark directly to the terminal as a visual indicator when commands complete successfully:

Bash

# Terminal success indicator
echo "All tasks complete \u2713"

Using these patterns helps maintain consistency across teams and reduces the cognitive load when scanning large documents or dashboards. When building templates, include the glyph in your sample outputs so readers see the intended symbol, not an empty box or placeholder.

Steps

Estimated time: 15-25 minutes

1
Identify your target environment
Determine whether you’re working on Windows, macOS, or Linux, and which editor or application your content will be used in. This choice dictates the insertion method you’ll rely on.
Tip: Keep a short note of the method you’ll use for each app in your workflow guide.
2
Choose a insertion method
Select the method you’ll apply most often: Alt code (Windows), Unicode input (macOS/Linux), or copy-paste. Prepare any prerequisites (enable Unicode input on macOS, ensure Num Lock and keypad use on Windows).
Tip: Unicode input is the most portable across apps and fonts.
3
Test in your target apps
Open a sample document and try inserting the tick with the chosen method. Check how the glyph renders in Word, Google Docs, Markdown editors, and code views.
Tip: If glyph rendering fails in a given app, switch to a reliable fallback (paste or ASCII).
4
Document the method for teammates
Add a short note in your style guide or team wiki detailing the recommended approach and any caveats for fonts, encoding, or platform differences.
Tip: Consistent guidance reduces confusion during onboarding.
5
Automate where possible
If you’re generating documents programmatically, embed the unicode escape (\u2713) or literal ✓ in templates to ensure consistency.
Tip: Automations save time and reduce human error.

Pro Tip: Test across all target apps to ensure the glyph renders identically.

Warning: Avoid relying on platform-specific ticks in data interchange without a defined encoding (UTF-8) and font support.

Note: Prefer Unicode or clipboard methods over hard-coded images for accessibility and portability.

Prerequisites

Required

Windows 10/11 or macOS (with UTF-8 support)
Required
Access to a text editor or word processor
Required
Basic keyboard navigation and typing
Required

Optional

Enable Unicode Hex Input on macOS↗
Optional
Optional: font that supports the checkmark glyph (e.g., Arial Unicode MS, Segoe UI Symbol)
Optional

Keyboard Shortcuts

Action	Shortcut
Insert checkmark via Windows Alt codeRequires a numeric keypad on Windows and a font that supports U+2713.	`Alt`+`2713`
Insert checkmark via Linux Unicode inputRequires Unicode Hex Input on Linux systems or editor support.	`Ctrl`+`⇧`+`U 2713 Enter`
Copy-paste a checkmark from clipboardCopy ✓ from a source and paste where needed	`Ctrl`+`C`

Questions & Answers

What is the quickest way to insert a tick on Windows?

The fastest approach is to use the Windows Alt code Alt+2713 to insert a checkmark in editors that support Unicode glyphs. If the keypad method isn’t available, copy a ✓ from another source. Always verify the font supports U+2713.

Can I insert a tick in Word or Google Docs easily?

Yes. In most Word processors and Google Docs, you can insert a checkmark via the Insert Symbol dialog or simply paste the glyph. For programmatic control, use a Unicode escape like \u2713 in templates that support it.

Are there platform differences I should know about ticks?

Yes. Windows, macOS, and Linux have different input methods for U+2713. macOS often requires Unicode Hex Input, Linux uses Ctrl+Shift+U, and Windows commonly uses Alt+2713. Always test in your target apps.

What should I do if the checkmark doesn’t display properly?

Check the font support for the glyph and ensure encoding is UTF-8. If necessary, switch to a fallback such as a text-based indicator (e.g., [x]) or copy-paste from a source that renders correctly.

Is there a universal keyboard shortcut for a tick?

No single universal shortcut exists across all platforms. Use OS-specific methods or copy-paste as a universal fallback, and document your preferred method in your team guide.