Small Business Copyright: Your Quick © Symbol Guide

Replace 2026 with the current year and CompanyName with your legal business name or brand. That’s the whole notice. Fastest ways to get the © symbol right now:

Copy-paste: © (copy directly from this page)
Windows: Hold Alt, type 0169 on the numeric keypad (Num Lock must be on)
Mac: Press Option+G
HTML: Type © in your markup

Those four methods cover most small business copyright situations. The sections below go deeper on each platform, web implementation, and common pitfalls.

Key Takeaways

Point	Details
Paste the notice now	Use © 2026 CompanyName. All rights reserved. and update the year each January.
Use OS shortcuts	Option+G (Mac) and Alt+0169 (Windows) work in every app, unlike AutoCorrect.
Prefer `©` in HTML	Named entity is readable and survives most CMS and pipeline serialization steps.
Set UTF-8 explicitly	Add `<meta charset="UTF-8">` and match your server Content-Type header to prevent broken glyphs.
Copyrighttoolkit	Use the copy-paste tool for instant symbol access and shortcut guides across platforms.

1. How to type © across every device and app
2. HTML entities, Unicode, and encoding for web pages
3. Storing and rendering © in components, templates, and CMS
4. Rendering, sizing, and accessibility for the © symbol
5. Diagnose and fix the most common © problems
6. Ready-to-use copyright notice templates for U.S. small businesses
7. Quick reference: shortcuts, entities, and copy-paste
8. Why trust this guide: Copyrighttoolkit’s approach
The one maintenance rule worth following
Copyrighttoolkit: copy the symbol and build your notice now
Sources

1. How to type © across every device and app

Getting the symbol right depends entirely on where you’re working. Here’s the breakdown by platform.

Windows

Alt+0169: Hold Alt, type 0169 on the numeric keypad (not the top-row numbers), release Alt. Num Lock must be on for this to work.
Emoji keyboard: Press Windows+. to open the emoji panel, search “copyright.”
Word/Outlook AutoCorrect: Type © and press Space. Word and Outlook convert © to © automatically in Rich Text and HTML email contexts. You can also use Insert → Symbol → Special Characters.

Mac

Option+G: The fastest method on any Mac keyboard, works system-wide.
Character Viewer: Press Control+Command+Space, search “copyright,” double-click to insert.
Word/Google Docs: Both apps recognize © + Space and convert it automatically in most document modes.

iOS and Android

iOS: On the standard keyboard, hold the letter C — © appears as an option in the pop-up.
Android: Open the symbol keyboard (?123 or !#1), then look in the special characters section.
Text replacement shortcut: On both platforms, set up a text replacement so typing something like cpr expands to ©. On iPhone: Settings → General → Keyboard → Text Replacement.

Pro Tip: OS-level shortcuts like Option+G and Alt+0169 work across every app. AutoCorrect conversions like © → © are app-specific and can fail in plain-text fields, code editors, or third-party tools. Learn the OS shortcut once and you’ll never be stuck.

2. HTML entities, Unicode, and encoding for web pages

Three methods work reliably for adding © to any web page. Each has a specific use case.

Method	Code	Best used when
Named entity	`©`	Source code is human-readable; team collaboration
Decimal reference	`©`	Passing through legacy parsers or CMS sanitizers
Hex reference	`©`	Developer preference; consistent with Unicode notation
Literal character	`©`	Page is confirmed UTF-8 end-to-end

The W3C HTML 4.01 specification defines © as the named entity for ©. Decimal (©) and hex (©) are valid alternatives — all three render identically in browsers.

UTF-8 encoding matters more than the entity choice. If your page serves a different encoding, a literal © character can render as Â© or a replacement glyph (�). Set encoding explicitly:

<meta charset="UTF-8">

On the server side, your HTTP response header should include:

Content-Type: text/html; charset=UTF-8

Both the meta tag and the header need to agree. The meta tag alone is not enough when a proxy or CDN strips or overrides headers.

Pro Tip: In multi-step pipelines — CMS editors, translation tools, component frameworks — prefer © or © over a literal © character. Named and numeric entities survive serialization steps that corrupt raw Unicode characters. If your string passes through three tools before rendering, a literal © is the most fragile option.

3. Storing and rendering © in components, templates, and CMS

Where you put the copyright string determines whether it breaks, doubles-escapes, or disappears in print.

Template vs. CSS-generated content

Keep the © character in your HTML markup, not in CSS content property. CSS-generated content can be excluded from print output and may be ignored by some accessibility tools. A footer like this is safe:

<footer>
  <p>&copy; 2026 CompanyName. All rights reserved.</p>
</footer>

Avoiding double-escaping

Double-escaping is when © renders literally as © in the browser instead of ©. It happens when a template engine or sanitizer escapes the ampersand a second time, turning © into ©.

Use textContent or text-node insertion in JavaScript rather than innerHTML for plain strings.
In React, JSX handles the literal © character fine: <p>© 2026 CompanyName</p> — or use {'©'} for the Unicode code point.
In Vue or Angular templates, the literal character or © in the template HTML both work; avoid passing the entity string through a JavaScript variable unless you’re using v-html deliberately.

i18n and componentization

If your site supports multiple languages, store the copyright string as a translatable key. The year and company name should be interpolated separately so translators don’t accidentally modify them:

copyright_notice = "© {year} {company}. All rights reserved."

Deployment checklist:

Confirm <meta charset="UTF-8"> is in every page <head>.
Verify the server sends Content-Type: text/html; charset=UTF-8.
Check the CMS field type — use a plain-text or HTML field, not a rich-text field that strips entities.
Add a smoke test: load the footer in a browser, view source, and confirm the entity or character is intact.
Run a screen-reader pass on the footer to confirm © is announced correctly.

4. Rendering, sizing, and accessibility for the © symbol

Font-dependent rendering

The © glyph looks different across fonts. In some typefaces it’s tight and compact; in others it sits heavy and oversized against surrounding text. Practical Typography recommends reducing an oversized © by roughly 40–55% and keeping it on the baseline to match the x-height of surrounding characters. Test your footer in at least three fonts: your primary web font, a system fallback (Georgia, Arial), and a monospace font if you use one in code blocks.

If you’re selling or distributing HTML templates, consistent glyph rendering across fonts is part of the product quality — worth testing before publishing. Platforms like Payhip for HTML templates are a common distribution channel where buyers expect polished output.

Accessibility

Screen readers generally announce © as “copyright” when it appears as a named entity or literal character in HTML. CSS-generated content is less predictable — some screen readers skip it entirely. For reliable behavior:

Keep © in the HTML text node, not in CSS.
Don’t wrap it in an aria-hidden element unless you’re also providing a visible text alternative.
Test with VoiceOver (Mac/iOS) and NVDA (Windows) during QA.

Pro Tip: During QA, copy the footer text and paste it into a plain-text editor. If © pastes as a question mark or box, your encoding is broken at the source. Fix encoding before worrying about visual sizing.

5. Diagnose and fix the most common © problems

Problem 1: © shows as Â© or ? (replacement glyph)

Check <meta charset="UTF-8"> is present in <head>.
Inspect the HTTP response header for Content-Type: text/html; charset=UTF-8.
Confirm the database or file is saved in UTF-8, not Latin-1 or Windows-1252.
Switch to © or © — entities are encoding-agnostic and sidestep this entirely.

Problem 2: © appears literally in the browser

Your template engine is double-escaping the ampersand. Find where the string is being processed and switch to a raw/unescaped output method.
In WordPress, avoid running the copyright string through esc_html() if it already contains an entity — use wp_kses() with an allowed entities list instead.
View source to confirm whether the HTML contains © (double-escaped) or © (correct).

Problem 3: CMS strips or rewrites the entity

Some WYSIWYG editors convert © to the literal © character on save, which is fine as long as encoding is UTF-8.
Others strip it entirely. Store the notice in a plain-text custom field or a theme template file rather than a page editor field.
After any CMS upgrade, re-check the footer output. Sanitizer rules change between versions.

Quick testing checklist:

View source: confirm © or © (not © or a question mark)
Check network headers in browser DevTools → Network → response headers
Copy-paste the footer text into Notepad or TextEdit (plain text) and verify © survives
Test on one Android and one iOS device for mobile rendering

6. Ready-to-use copyright notice templates for U.S. small businesses

The minimal notice every small business needs:

Replace 2026 with the current year and CompanyName with your legal entity name or registered brand. That’s the legally recognized form in the United States.

Use case	Template
Website footer	`© 2026 CompanyName. All rights reserved.`
Ecommerce footer	`© 2026 CompanyName. All rights reserved.
Invoice or proposal	`© 2026 CompanyName. Confidential. Not for distribution.`
Product packaging	`© 2026 CompanyName`
Marketing materials	`© 2026 CompanyName. All rights reserved.`
Book or publication	See the book copyright page guide for full templates

A few variants worth knowing:

With a range of years: © 2019–[current year] CompanyName signals the business has been operating since 2019. Update the end year annually if used.

Store the notice string in your site template or a CMS global field, not in individual page content. That way, updating the year takes one edit instead of dozens.

7. Quick reference: shortcuts, entities, and copy-paste

Keyboard shortcuts

Windows (numeric keypad): Alt+0169 (Num Lock on)
Windows (no keypad): Windows+. → search “copyright”
Mac: Option+G
Mac (Character Viewer): Control+Command+Space → search “copyright”
Android: Symbol keyboard → special characters

HTML entities

Named: ©
Decimal: ©
Hex: ©
Unicode code point: U+00A9

Copy-paste ready

One-line test: Paste © into a plain-text editor. If it shows as © — you’re good. If it shows as a box or Â© — your encoding needs fixing.

8. Why trust this guide: Copyrighttoolkit’s approach

Copyrighttoolkit is built around one practical goal: give creators, business owners, and developers the exact tools they need to use copyright symbols correctly, without wading through legal theory.

The guides and copy-paste tools on Copyrighttoolkit are maintained by the support team, verified against platform documentation (Microsoft Support, W3C, MDN), and tested across common stacks including WordPress, React, and standard HTML pages. Every shortcut listed here has been confirmed against current OS behavior.

The brand’s copy-paste tools, shortcut references, and symbol guides cover ©, ®, ™, and related characters. If you work with trademark symbols alongside copyright, the TM vs SM guide and the registered trademark symbol page cover the distinctions.

Shortcuts verified on Windows 11 and macOS Ventura/Sonoma
HTML methods tested in Chrome, Firefox, and Safari
CMS guidance covers WordPress (classic and block editor) and common headless setups
Accessibility notes reflect VoiceOver and NVDA behavior

The one maintenance rule worth following

Treat the copyright string the same way you’d treat any other UI string in your codebase: put it in version control, set encoding explicitly from day one, and add a smoke test to your deployment pipeline. The symbol itself never changes, but the year does, and CMS upgrades routinely alter how sanitizers handle entities. A five-minute check after every major platform update prevents the kind of broken footer that quietly sits there for months before anyone notices.

Copyrighttoolkit: copy the symbol and build your notice now

The fastest path from this article to a working copyright notice is a single copy-paste. Copyrighttoolkit gives you that directly — no setup, no account, just the symbol ready to copy and the shortcut reference to bookmark.

The symbol copy-paste tool covers © and related circled-C variants in one place. The main Copyrighttoolkit site has shortcut guides, HTML references, and notice generators for every platform. If you’re working on a book or longer publication, the book copyright page templates give you a full-page format ready to adapt.

Pick the tool that fits your next task and use it now.