Radio Button Emoji

🔘 is a radio button in its selected state. A smaller dot inside a larger circle, used to show one option has been picked from a group of mutually exclusive choices. On Emojipedia it's catalogued as Radio Button and approved in Unicode 6.0 (2010).

The funny thing is most people who send this emoji have never touched an actual radio button. The name comes from the push-button presets on old car radios: mechanical rows of five or six buttons where pressing one physically popped the previously selected one back out. Press "AM" and the "FM" button pops. Press the second preset and the first preset pops. Mutual exclusion, enforced by springs and metal levers.

That behavior became the template for a software widget. Ted Kaehler built the first digital radio buttons in 1975 for the BitRectEditor in Smalltalk. Xerox Star (1981) and Apple Lisa (1983) shipped them to consumers. RFC 1866 standardized `<input type="radio">` for HTML 2.0 in 1995. By 2010, Unicode added the icon to the emoji keyboard.

So 🔘 is a skeuomorphic ghost. It's a digital icon of a software widget inspired by a mechanical button named after a device (the radio) that most people under 30 only know as the thing inside an AirPod.

People use 🔘 three ways, and two of them are unrelated to radios.

As a bullet point. The main use in texting. People drop 🔘 at the start of list items to make a message feel tidier than a dash would. It reads visually as "a small thing I am noting," similar to how ▪️ or ● get used. This shows up in checklists, itineraries, and grocery messages. No deep meaning, just a prettier bullet.

As a selection marker. When someone is offering options, 🔘 means "pick one." A friend texting "🔘 pizza 🔘 tacos 🔘 sushi — where are we going?" is using the emoji's literal meaning, a radio button. This is the closest the emoji gets to its Unicode name.

As a small dark dot. Because 🔘 is so visually understated (a dot with a rim, not much color), it gets used as a neutral accent. Graphic captions, minimalist Instagram bios, decorative separators. Pairs well with monochrome aesthetics that avoid the intensity of 🔴 or the starkness of ⚫.

In workplace chat (Slack, Teams, Discord), 🔘 rarely shows up on its own. It lives inside "poll" syntax some bots emit, or it appears in technical docs where someone is literally describing a radio button in a UI. When an engineer types 🔘, they usually mean the widget.

🔘 has two overlapping origin stories: the widget and the emoji.

The widget (1930s to 1995). In 1936, Galvin Manufacturing (later Motorola) introduced push-button tuning on their car radios. A mechanical row of buttons let drivers pre-select stations. Pressing one button physically ejected the previously pressed one. This "press one, pop the others" behavior became the design metaphor. In 1975, Ted Kaehler built digital "RadioButtons" for the BitRectEditor in Smalltalk at Xerox PARC. Xerox Star (1981) and Apple Lisa (1983) popularized the visual. In 1995, the HTML 2.0 specification (RFC 1866) standardized <input type="radio"><input type="radio">, and radio buttons went global.

The emoji (2007 to 2010). Radio Button was proposed in Unicode document L2/07-257 (2007) and refined in L2/09-026 (2009). It was one of several "UI chrome" glyphs added because Japanese mobile carriers (DoCoMo, KDDI, SoftBank) used interface symbols as emoji on their feature phones. When Unicode 6.0 shipped in October 2010, 🔘 came along for the ride with hundreds of other Japanese carrier glyphs.

The widget is 90 years old. The emoji is 15 years old. The word "radio" in both refers to an object most of the people texting 🔘 today have never seen.

1. 1936Galvin Manufacturing (later Motorola) introduces push-button tuning on car radios. The mechanical ancestor of every radio button ever.↗
2. 1975Ted Kaehler builds digital "RadioButtons" for the BitRectEditor in Smalltalk at Xerox PARC. The first software radio button.↗
3. 1981Xerox Star ships with radio buttons in its GUI, the first commercial system to popularize the design.
4. 1983Apple Lisa ships with radio buttons, bringing the widget to a consumer audience.
5. 1995RFC 1866 (HTML 2.0) standardizes `<input type="radio">`. Radio buttons become a universal web primitive.↗
6. 2010Unicode 6.0 adds RADIO BUTTON (U+1F518) as part of the Miscellaneous Symbols and Pictographs block.
7. 2015Emoji 1.0 is formalized (June 9, 2015), locking 🔘's emoji status across platforms.

🔘 is one of the least culturally variable emojis. It's a piece of UI chrome, not a symbol, so it doesn't carry religious, political, or regional baggage the way colored circles do.

Japan: The emoji's lineage is Japanese. Early Japanese carrier phones used UI glyphs as emoji for weather forecasts, transit info, and form elements. 🔘 was part of that generation of "system" emojis, and it still appears in Japanese form-heavy contexts more than anywhere else.

Western workplaces: 🔘 shows up in technical documentation and bug reports. When a QA engineer writes "the 🔘 doesn't work on iOS," they mean the actual radio button in the interface, not a metaphor.

Global messaging: For casual texters everywhere, 🔘 is a neat bullet or a "pick one" marker. The Unicode name is widely ignored. In a 2023 scan of Twitter messages using 🔘, the majority of uses had nothing to do with radio buttons as a UI concept; they were list decorations or aesthetic accents.

Accessibility contexts: NVDA, VoiceOver, and JAWS announce the emoji as "radio button." For screen reader users, 🔘 in a message reads exactly like the name of the widget, which can be confusing if the sender meant it as a bullet.

• •The radio button's name comes from 1936 Motorola car radio presets, where pressing one button physically popped the others out. The mechanical behavior was so intuitive that 90 years later, software still copies it.
• •The first digital radio buttons were built by Ted Kaehler at Xerox PARC in 1975 for the BitRectEditor in Smalltalk. Kaehler later worked on HyperCard and helped develop Squeak.
• •🔘 was added to Unicode 6.0 in October 2010 alongside roughly 1,000 other emojis, most of them imported from Japanese carrier sets (DoCoMo, KDDI, SoftBank) to harmonize global emoji support.
• •The HTML spec for radio buttons was standardized in RFC 1866 (HTML 2.0, 1995). The <input type="radio"><input type="radio"> element has survived unchanged for 31 years, one of the most stable pieces of the web platform.
• •Screen readers announce 🔘 as "radio button", which can confuse users who receive the emoji as a bullet. NVDA, JAWS, and VoiceOver all name the widget explicitly.
• •The Apple Lisa (1983) and the Xerox Star (1981) both shipped with radio buttons, but their visual styles differed. Lisa buttons were rounder and more 3D; Star used flat outlined circles. Modern design has cycled through both looks multiple times.
• •Mac HIG (Human Interface Guidelines) recommends radio buttons only for 2-7 options. Above 7, NN/G research says dropdowns are more efficient because scanning a long radio list is slower than opening a menu.

• •Motorola's 1936 car radio button — The Galvin Manufacturing push-button tuner gave the widget its name. The mechanical design (press one, others pop out) was already intuitive by the 1940s. Nine decades later, the metaphor still works.
• •Ted Kaehler's Smalltalk radio buttons (1975) — At Xerox PARC, Kaehler built the first digital radio buttons for the BitRectEditor. The choice to copy a 1930s car dashboard into a 1970s operating system set the template for every GUI form ever built.
• •Apple Lisa and Xerox Star (1981-1983) — The first mainstream computers to ship with radio buttons. Both went commercial failures, but the widget outlived them. Today there are radio buttons in every browser, every settings panel, every survey.
• •RFC 1866 (1995) — When HTML 2.0 standardized `<input type="radio">`, the widget became a fundamental web primitive. Every online form, every Google Docs toggle, every checkout flow inherits from that 1995 spec.

• •🔘 sits at U+1F518U+1F518 in the Miscellaneous Symbols and Pictographs block. Official Unicode name: RADIO BUTTONRADIO BUTTON.
• •Common shortcodes: :radio_button::radio_button: on GitHub, Discord, and Slack.
• •For actual radio-button UI, always use native HTML (<input type="radio"><input type="radio">) or role="radio"role="radio" inside a role="radiogroup"role="radiogroup". ARIA expects arrow-key navigation within the group and Space to select.
• •When building custom radio components, remember the "select all that apply" vs "select one" distinction. Use a <fieldset><fieldset> with a <legend><legend> for grouped radios so screen readers announce the group context.
• •🔘 has no skin-tone modifiers, ZWJ variants, or regional forms. It's a single codepoint with identical behavior on every platform.

See the full Emoji Developer Tools guide for regex patterns, encoding helpers, and more.