Can You Use Emojis Commercially?

Can You Use Emojis Commercially? Licences by Emoji Set

Apple's App Store rules say it plainly: "Apple emoji may not be used on other platforms or embedded directly in your app binary." Apple publishes no licence that lets you print its emoji artwork in a book, on a T-shirt or in a logo, so for commercial work you pick a set whose owner did publish one. Google's Noto Emoji fonts carry the SIL Open Font License, Twemoji graphics are CC BY 4.0, OpenMoji is CC BY-SA 4.0, and Microsoft's Fluent Emoji repository is MIT. The emoji character itself, the code point you type, belongs to no one in that sense.

The Unicode Consortium, which assigns those code points, says it "is not a designer nor purveyor of emoji images" and "does not negotiate licenses for their use." Requests to use a vendor's emoji pictures, it adds, "should be directed to those vendors." So the 😀 in a text message is two things at once: a number in a shared standard, and a small drawing made by Apple, Google, Samsung, Microsoft or someone else. Every commercial question below turns on which of the two you are actually using.

The number is shared, the drawing has an owner

U+1F600 GRINNING FACE is a code point. Typing it into a caption, a product description or a tweet sends that number, and the reader's device draws it with whatever emoji font it has. An iPhone reader sees Apple's grin, an Android reader sees Google's, a Windows reader sees Microsoft's. You never shipped anyone's artwork; you shipped text. Unicode's own data files, including the emoji lists, are published under the Unicode License V3, which grants permission "to deal in the Data Files or Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies," provided the copyright and permission notice travels with the copies or their documentation. That licence covers Unicode's data, not any vendor's pictures.

The picture is different. Unicode's "Emoji Images and Rights" page says the coloured images in its charts are "made available by the respective vendors for use in Unicode emoji documents and charts, or are marked as available for non-commercial reuse," and that copying them "without the prior written permission of the owner, is strictly prohibited." The moment you export a PNG of an emoji, place a screenshot of one in a print layout, or embed an emoji font in a PDF, you are distributing a specific drawing, and the drawing's owner decides what you may do with it.

Where text quietly becomes artwork

The switch from text to artwork happens in ordinary software, often without anyone noticing:

• Exporting a PDF. Type an emoji in InDesign, Word or Pages on a Mac, export a PDF, and the layout app takes the glyph from Apple Color Emoji, the emoji font that ships with macOS. The PDF now carries Apple's drawing, either as an embedded font subset or as an image.
• Exporting an image or video. A social card, YouTube thumbnail or caption burned into video is a picture of whatever emoji font your machine used. A viewer's phone does not redraw it.
• Screenshots. A screenshot of a chat thread contains the artwork of the phone that took it.
• Live text on the web. An emoji typed into the HTML of a web page stays text. Each visitor's own system font draws it. That is the one common route where you are not distributing anyone's emoji art, unless you also serve an emoji web font or image files.

On a Mac you can check what the font file itself says. We read the Apple Color Emoji font on our macOS 26.6.2 test machine on October 31, 2026: its copyright string is "© 2011-2026 Apple Inc. All rights reserved," its version string is 21.4d3e1, it holds 3,844 glyphs stored as bitmap images, and its embedding field is set to 0x0004, the value the OpenType specification gives to "print and preview" embedding. Microsoft's font FAQ describes that setting: an app may embed the font in a saved document, but "the document must be locked for editing." That flag says whether a PDF may carry the font. It does not grant any right to print the result for sale.

Does copyright reach a tiny smiley at all?

US copyright law gives simple shapes very little protection. The Copyright Office's Compendium, chapter 300, lists among the "familiar symbols and designs" it will not register "simple emoticons such as the typical smiley face (☺)," along with hearts, stars, arrows and keyboard symbols. It also says the law "does not protect typeface or mere variations of typographic ornamentation or lettering."

Neither line settles the question for a vendor's emoji. Apple's or Samsung's drawings have shading, gradients, highlights and detailed faces, which is a long way from a ☺ glyph. The Compendium was not written about them, and we know of no Copyright Office statement or US court ruling that decides whether a modern colour emoji drawing is protected. Treat vendor artwork as owned, as the vendors and Unicode both do, rather than betting a print run on a registration rule written for simple symbols.

Nine emoji sources and the terms each one publishes

Each row below comes from a licence file, terms document or guideline we read on October 31, 2026. Where a company publishes nothing, the row says so.

The table shows a clean split. Phone-maker emoji (Apple, Samsung) come with no public grant at all. Open sets (Noto, Twemoji, OpenMoji, Fluent) can be used commercially and differ only in what you owe back: a licence file, a credit line, share-alike, or a notice. JoyPixels sells permission by use and volume.

What each job needs: a use-by-use matrix

Quote a job against these rows. "Not granted" means no published text from the owner gives you that right, not that the owner has forbidden it in writing.

Two rows surprise people. The Windows font column is generous for print, logos and images because Microsoft's FAQ says its general rules "apply to all the fonts installed with Windows as system-wide resources," which includes the emoji font. And the JoyPixels column, the only paid option, is the most restrictive for merchandise and logos.

Apple's emoji: what Apple's own documents say

Apple's position has to be pieced together from three documents, because there is no single emoji licence page.

App Review Guidelines, section 4.5.6. "Apps may use Unicode characters that render as Apple emoji in their app and app metadata. Apple emoji may not be used on other platforms or embedded directly in your app binary." That is permission to type emoji as text in an iOS app and its App Store listing, and a ban on bundling the artwork itself or using it elsewhere. The guidelines we read were last updated October 16, 2026.

Section 5.2.5, Apple Products. "Apps and extensions, including third-party keyboards and Sticker packs, may not include Apple emoji." This closes the obvious workaround of shipping Apple's drawings as stickers.

The macOS software licence, section 2E. Apple Color Emoji is a font bundled with macOS, so the font clause applies: you "may use the fonts included with the Apple Software to display and print content while running the Apple Software," and may embed fonts in content only "if that is permitted by the embedding restrictions accompanying the font." We read this in the current macOS licence (document EA2005) and the macOS Tahoe 26 licence. The clause grants printing. It says nothing about selling what you print, using the output as a logo or reproducing it on merchandise, and no Apple page we read fills that gap. Our guide to Arial and other system fonts reads the same clause for text fonts and reaches the same "not addressed" result for logos and sales.

That silence matters because the App Review text shows what Apple thinks of its artwork leaving Apple devices. The safe reading for a book cover, merch line, ad or logo is that Apple has given no permission, and the only way to get one is to ask Apple. We found no published Apple process for that request.

Memoji and Genmoji have their own, stricter clause

Memoji and Genmoji are not Unicode emoji, and Apple wrote a specific rule for them. Section 2R of the current macOS licence, "System Characters," lets you use "the Genmoji and Memoji characters included in or created with the Apple Software" while running the software and "to create your own original content and projects for your personal, non-commercial use." It then excludes "use, reproduction, display, performance, recording, publishing or redistribution of any of the System Characters in a profit, non-profit, public sharing or commercial context."

That last list is broad: even a non-profit or public post falls outside it. The macOS Sequoia licence had the same clause naming only Memoji; the Tahoe and later texts add Genmoji. So a Genmoji you generated for a product launch, or a Memoji of yourself on a course thumbnail, is outside the licence as written, even though you prompted or built it yourself.

Samsung and the other phone-maker sets

Samsung's emoji appear on Galaxy phones, but we know of no public licence for the artwork, and we found no Samsung terms that address it. The same goes for the emoji drawn by Meta for WhatsApp and Facebook and by other platform vendors. With no published grant, the position is the same as Apple's: the drawings are owned, Unicode tells you to ask the vendor, and nothing in writing lets you print them on a product.

If a design brief says "use the Samsung emoji" or "use the WhatsApp one," the practical answer is a different set in a similar style, or an original drawing.

Google Noto Emoji: an open font with a split image licence

Google publishes two emoji fonts on Google Fonts: Noto Color Emoji and the monochrome, variable Noto Emoji. The OFL.txt file in Google's google/fonts repository for each family opens with "This Font Software is licensed under the SIL Open Font License, Version 1.1," with copyright lines of "Copyright 2021 Google Inc." for the colour font and "Copyright 2013 Google LLC" for the monochrome one.

The OFL is a font licence, so its rules are about the font file. Condition 1 says the font may not be "sold by itself." Condition 2 lets it be "bundled, redistributed and/or sold with any software" as long as the copyright notice and licence go with it. The clause that matters most for designers is the last sentence of condition 5: "The requirement for fonts to remain under this license does not apply to any document created using the Font Software." A book, poster, T-shirt graphic or video made with Noto Color Emoji is a document created with the font, so it is not bound by the OFL.

The googlefonts/noto-emoji GitHub repository adds a wrinkle. Its README says "Emoji fonts (under the fonts subdirectory) are under the SIL Open Font License, version 1.1" and "Tools and most image resources are under the Apache license, version 2.0," with flag images "in the public domain or otherwise exempt from copyright." But the LICENSE file at the repository root, which the README links as the Apache licence, contained the OFL text when we fetched it on October 31, 2026, and GitHub's own licence detection reports OFL-1.1 for the repository. If you use the PNG or SVG files rather than the font, save both the README and the LICENSE file with your project record, and note the date. Either licence allows commercial use; they differ in the notice you keep.

When Noto is the right choice

Noto suits print and ebooks best, because the font can be embedded in a PDF and no credit is owed in the finished document. Its style is the one Android users see, which also makes it the closest open match to "the phone emoji look" for a general audience. For the font licence types in general, our commercial font licensing guide lays out how desktop, web and app rights split.

Twemoji: CC BY 4.0, maintained outside Twitter

Twemoji started at Twitter in 2014. The copyright notice in the current MIT licence file reads "Copyright (c) 2022–present Jason Sofonia & Justine De Caires" and "Copyright (c) 2014–2021 Twitter," and the project's README lists both, along with Bryan Haggerty, as "ex-Twitter." The jdecked/twemoji repository is where new releases appear: its README describes Twemoji v17.0, following the Unicode 17.0 and Emoji 17.0 specifications. The original twitter/twemoji repository's README still describes v14.0. GitHub did not mark the Twitter repository as archived when we checked, so "archived" is not accurate, but it is not where current emoji are added.

The licence split is stated in the README: "Code licensed under the MIT License" and "Graphics licensed under CC-BY 4.0." The LICENSE-GRAPHICS file is the full Creative Commons Attribution 4.0 legal code.

What CC BY 4.0 asks of you

Section 3(a) of CC BY 4.0 lists what you keep when you share the graphics: identification of the creator "in any reasonable manner requested by the Licensor," a copyright notice, a notice that refers to the licence, a disclaimer notice, and a link "to the extent reasonably practicable." You must also "indicate if You modified the Licensed Material." Section 3(a)(2) lets you meet those conditions "in any reasonable manner based on the medium, means, and context."

The Twemoji maintainers say what reasonable means to them. Their README calls the Creative Commons attribution guide "a bit onerous" and says the project "will accept a mention in a project README or an 'About' section or footer on a website." In a mobile app, a Settings or About screen is fine, and "a mention in the HTML/JS source" is also acceptable to them. For a printed book, the copyright page is the equivalent of the About screen. For a video, the description box.

Section 2(b)(2) of the same licence says "Patent and trademark rights are not licensed under this Public License." Twemoji's graphics are CC BY; the name Twitter and its marks are not part of that grant. Our Creative Commons explainer covers the attribution parts of section 3 in more detail.

OpenMoji: free, with share-alike strings

OpenMoji, from the HfG Schwäbisch Gmünd design school, licenses its graphics under CC BY-SA 4.0 and its code under LGPL-3.0. The attribution its README suggests reads: "All emojis designed by OpenMoji – the open-source emoji and icon project. License: CC BY-SA 4.0." The README asks for credit in "your project README, the 'About' section or the footer on a website/in mobile apps."

Commercial use is allowed. The catch is section 3(b) of BY-SA: when you share Adapted Material, "The Adapter's License You apply must be a Creative Commons license with the same License Elements, this version or later, or a BY-SA Compatible License." The licence defines Adapted Material as material in which the original is "translated, altered, arranged, transformed, or otherwise modified in a manner requiring permission." That definition singles out only music: synching a musical work with a moving image always counts as an adaptation. It says nothing similar about placing an unmodified emoji in a book or video.

So the practical line runs between using and redrawing. An unmodified OpenMoji placed next to text in a guidebook is used as is, with credit. An OpenMoji you recolour, redraw or merge into a mascot is an adaptation, and if you share it, your version must carry BY-SA too, which means anyone can reuse your mascot under the same terms. That outcome suits community and education projects. It rarely suits a brand.

Microsoft: Fluent Emoji on GitHub and Segoe UI Emoji in Windows

Microsoft offers emoji under two unrelated sets of terms, and "Microsoft emoji" questions usually go wrong by mixing the two up.

Fluent Emoji. The microsoft/fluentui-emoji repository publishes Microsoft's Fluent emoji designs, and its LICENSE file is the MIT License, "Copyright (c) Microsoft Corporation." MIT grants the rights "to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies," on one condition: "The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software." For an app or website that ships the files, that notice goes in the licences screen or a bundled text file. For a printed product, a short notice on the copyright page or packaging is the cautious way to meet it. The repository has no separate trademark statement, so the MIT text is the whole grant.

Segoe UI Emoji. The emoji font in Windows is covered by Microsoft's Font redistribution FAQ for Windows (last updated November 19, 2024). The FAQ answers "Do these general use guidelines apply to the symbol and emoji fonts supplied with Windows?" with "Yes, they apply to all the fonts installed with Windows as system-wide resources." Those general rules allow a lot of output: Microsoft does "not place any restrictions on what you do with print output," does "not restrict you from selling the things you print and make," treats graphic files "as being essentially the same as printing," treats video captions the same way "providing the captions or text is rendered as a bitmap image," and does "not restrict you from making logos." Each answer carries one exception: none of it applies if the app you design in is "specifically licensed for home, student, or non-commercial use."

What the FAQ does not allow is moving the font. "You may not copy them to other computers or servers, and you may not convert them to other formats, including bitmap formats, or modify them." For apps and games, a pre-rendered image is allowed only if it is "an image of a word, phrase or passage of text," and converting the font into individual bitmap glyphs is not. So a designer on Windows can print a mug with a Segoe UI Emoji heart on it. A developer cannot pull the emoji out of the font as a sprite sheet for a game.

JoyPixels: paid licences with unit caps

JoyPixels sells its emoji under tiered agreements, all at version 11.0.0 dated June 24, 2026. Its pricing page on October 31, 2026 described the free tier as "Personal use only. Not for commercial use," Premium as for "businesses up to $1 million in annual revenue," and Pro as for "businesses up to $50 million in annual revenue." Prices shown there were discounted at the time, so check the live page rather than relying on a figure here.

The free agreement is narrow. Section 3.2 reads "PERSONAL USE ONLY - no commercial use (or money generating use)," images must be PNG no larger than 64 by 64 pixels, and section 3.5 rules out business use, advertising, and "any charity or fundraising purpose." Even a personal fundraiser is outside it.

The Pro agreement (the text we read in full) allows display in websites, apps, social media content, online and print advertising, promotional items "not for resale," and "Self published digital books or ebooks intended for sale," up to a maximum of 10,000 units. Physical goods get a much smaller allowance: "Tangible/physical products for testing purposes only," up to 100 units, including print-on-demand. Section 3.4 then lists what Pro does not cover, including television, streaming shows and films, creative software and resold templates, "open source projects or cryptocurrency/blockchain/NFT projects," use for a client, and three lines that matter to designers:

• "(Q) Use it in a logo."
• "(P) Register as a trademark any of the JoyPixels Properties, or any products or works that include the JoyPixels Properties."
• "(R) Modify it including any changes to design, color, shape, etc." without prior written permission.

The agreement also says that if you breach it you will "pay us 100% of all revenue you've received" from the items involved. A merch seller or print publisher who assumed "paid" meant "unlimited" would be outside the Pro text after the 100th unit.

Logos built on an emoji

A logo is the riskiest place to use an emoji, and the reasons differ by set.

• Apple and Samsung artwork: no grant to use it at all, and a logo is exactly the sort of commercial reuse the App Review rules show Apple guarding.
• JoyPixels: explicitly forbidden, along with registering anything that contains it as a trademark.
• OpenMoji: allowed, but a modified mark has to be shared under CC BY-SA, which lets competitors reuse it.
• Noto, Twemoji, Fluent and Windows Segoe UI Emoji: the licence text permits it. Twemoji's CC BY terms still expect a credit wherever the mark is shared, and Fluent's MIT notice has to travel with copies of the files, which few brands want on a business card. None of these licences gives you exclusive rights, though. Every other business can use the same smiley, so the emoji part of your mark is not distinctive and cannot be yours alone. Creative Commons states that trademark rights are not licensed, and the OFL lets authors reserve font names.

That last point is why a stock emoji works badly as the core of a brand even when it is legal. Our guide to copyright and trademark for logos explains why distinctiveness matters, and the USPTO trademark guide covers what the office checks when you file. If a brand wants a smiling face, an original pictograph drawn for the client avoids all of the above.

Four licensing routes for one picture book

Take a self-published children's book: 32 pages, 40 emoji used as small illustrations, an ebook on two stores, and a print-on-demand paperback expected to sell a few hundred copies in its first year. The designer works on a Mac.

Route 1, the default. The designer types emoji into the layout app and exports. Every emoji in the PDF is Apple's drawing. Apple's macOS licence grants "display and print," and its App Review text shows Apple does not want its emoji used off its platforms. Nothing permits selling copies. Outcome: not covered.

Route 2, Noto Color Emoji. The designer installs Noto Color Emoji from Google Fonts and sets the emoji in it. The finished files are documents "created using the Font Software," so the OFL does not follow them, and no credit is owed. The designer keeps the OFL.txt file in the project archive. Outcome: covered for the ebook and every print copy.

Route 3, Twemoji images. The designer places Twemoji SVGs as artwork. CC BY 4.0 allows sale. The copyright page carries one line, for example: "Emoji graphics: Twemoji by the Twemoji authors, licensed CC BY 4.0, creativecommons.org/licenses/by/4.0/." If any emoji was recoloured, the line adds "modified." Outcome: covered.

Route 4, JoyPixels Pro. The ebook fits under "Self published digital books or ebooks intended for sale," up to 10,000 units. The paperback is a "tangible/physical product," allowed only for testing and capped at 100 units. A few hundred paperbacks would need an Enterprise licence. Outcome: ebook covered, paperback not, at a monthly cost.

Routes 2 and 3 cost nothing and cover both formats. The real work is swapping the font before export and checking the proof, because a single emoji that falls back to Apple Color Emoji puts route 1 back into the file. Searching the PDF's font list in Acrobat (File, Properties, Fonts) shows whether an Apple Color Emoji entry is embedded anywhere.

Video, streams and social posts

Video sits between print and live text. A caption typed in an editor on a Mac and burned into the video is Apple's drawing in every frame, just as in a PDF. A caption typed into YouTube's own caption track or a post's text field stays text, drawn on each viewer's device.

• Twemoji or OpenMoji in a video: put the credit line in the description, which is the reasonable "medium, means, and context" location for most platforms.
• Segoe UI Emoji: Microsoft's FAQ allows captions and text in video "providing the captions or text is rendered as a bitmap image, and the font files themselves are not embedded within the video file."
• JoyPixels Pro: "Social media content" including videos and thumbnails is allowed, but a "television/streaming show or film/movie production including documentaries and music videos" and TV or streaming ads need Enterprise.
• Memoji or Genmoji avatars: Apple's clause excludes "recording, publishing" in any commercial or public-sharing context.

Our guide to free stock videos for commercial use covers the footage side of the same projects.

Apps, keyboards and websites

On iOS, Apple's 4.5.6 rule sets the limit: emoji as Unicode text in your interface and App Store metadata are fine, and the system draws them. Bundling Apple's art in the binary is not, and 5.2.5 bars Apple emoji from keyboards and sticker packs entirely.

For an app that needs its own emoji images, so they look the same on every platform, the open sets work: Noto's font bundled with its OFL text, Twemoji or OpenMoji with credit in the About or Settings screen, or Fluent with the MIT notice in your open-source licences list. JoyPixels Pro allows use in your own app but not an app whose "sole purpose or primary purpose" is the emoji, such as a sticker or keyboard app.

On the web, typed emoji are text. If you replace them with image files for consistency, which is what the Twemoji JavaScript library was built to do, the credit moves to the footer or About page. Shipping emoji as SVG adds file-size work too; our SVG optimization guide covers that.

Keeping a record of which emoji you shipped

Licences change, repositories move, and a client may ask years later where the smiley on their packaging came from. For each project that ships emoji artwork, save:

1. The set name and version or release (for example, "Twemoji v17.0" or "Noto Color Emoji from google/fonts, OFL.txt").
2. A copy of the licence text and, for Noto images, the README as it read on the day.
3. The exact credit line used, and where it appears (copyright page, description, About screen).
4. For JoyPixels, the agreement version, the tier, and the unit count against its caps.
5. A note that no Apple, Samsung or other phone-maker emoji artwork is in the final files, with the font list from the PDF or export as evidence.

This is practical guidance for working designers, not legal advice. The asset register in our licensing checklist for design assets has a row format that fits emoji alongside fonts, icons and photos, and the free icons for commercial use guide is the next stop if a project needs interface symbols that are not emoji at all: the same open licences, with sets drawn for buttons and menus rather than conversation.

Emoji licensing questions

Can I use Apple emojis in a book I sell?

Apple publishes no licence that allows it. Its macOS licence lets you display and print with its fonts while running macOS, and its App Review Guidelines say Apple emoji "may not be used on other platforms." Set the emoji in Noto Color Emoji or use Twemoji images instead.

Can I put an emoji on a T-shirt I sell?

Yes, with an open set. Noto Color Emoji (OFL) needs no credit on the shirt, Twemoji (CC BY 4.0) needs a reasonable credit such as one on the product listing, and Fluent Emoji (MIT) needs its notice. JoyPixels Pro limits physical products to 100 test units.

Are emojis copyrighted?

The code points are a public standard, and Unicode's data is under an open licence. The drawings belong to whoever made them. The US Copyright Office will not register simple emoticons like ☺, but detailed vendor artwork is a different matter, and no rule we found treats it as free.

Can I use an emoji in my logo?

The licence text of Noto, Twemoji, Fluent and Microsoft's Windows font FAQ permits it. JoyPixels forbids it, OpenMoji forces share-alike on a modified mark, and Apple gives no permission. A shared emoji also cannot be exclusive to your brand.

Do I need permission to use emoji in a YouTube video?

Typed into YouTube's text fields, no: each viewer's device draws them. Burned into the video from a Mac, the frames contain Apple's artwork. Use an open set and credit it in the description, or render Windows Segoe UI Emoji as images.

Is Twemoji still free to use now that Twitter is X?

Yes. The graphics remain under CC BY 4.0, and new releases come from the jdecked/twemoji repository, maintained by former Twitter designers and now at v17.0. The licence does not grant any Twitter or X trademark.

Can I use Memoji or Genmoji in marketing?

Not under Apple's licence. Section 2R allows them only for "personal, non-commercial use" and excludes publishing in "a profit, non-profit, public sharing or commercial context."

Where each emoji term comes from

• Apple, App Review Guidelines, last updated October 16, 2026, read October 31, 2026: sections 4.5.6 and 5.2.5.
• Apple, macOS software licence agreement, document EA2005, read October 31, 2026: sections 2E (Fonts) and 2R (System Characters); compared with the macOS Tahoe 26 and macOS Sequoia licences for the Memoji and Genmoji wording.
• Apple Color Emoji font file from macOS 26.6.2, read October 31, 2026: copyright string, version 21.4d3e1, 3,844 glyphs, embedding field 0x0004.
• Unicode Consortium, Emoji and Dingbats FAQ and Emoji Images and Rights, read October 31, 2026; Unicode License V3, read October 31, 2026.
• Google, Noto Emoji repository README and LICENSE, read October 31, 2026; Google Fonts Noto Color Emoji OFL.txt and Noto Emoji OFL.txt, read October 31, 2026.
• Twemoji, jdecked/twemoji README, LICENSE and LICENSE-GRAPHICS, read October 31, 2026; the original twitter/twemoji README and repository status, read October 31, 2026.
• OpenMoji, hfg-gmuend/openmoji README and LICENSE.txt, read October 31, 2026.
• Microsoft, fluentui-emoji LICENSE, read October 31, 2026; Font redistribution FAQ for Windows, last updated November 19, 2024, read October 30, 2026.
• JoyPixels, pricing and licence page and the Free and Pro licence agreements, version 11.0.0 dated June 24, 2026, read October 31, 2026.
• Creative Commons, Attribution 4.0 and Attribution-ShareAlike 4.0 legal code, as shipped in the Twemoji and OpenMoji repositories, read October 31, 2026.
• US Copyright Office, Compendium of U.S. Copyright Office Practices, Third Edition, chapter 300, sections 313.3(D) and 313.4(J), January 28, 2021 revision, read October 31, 2026.
• Not found or not checked: any Samsung, Meta or other phone-maker emoji licence; the JoyPixels Premium and Enterprise agreement texts.