Asterisk or star—two names, one symbol, yet the gap between them shapes everything from your Wi-Fi password to a billion-dollar telecom stack. Knowing when to call it “asterisk” and when to call it “star” saves debugging hours, prevents UX confusion, and keeps legal teams from red-lining your docs.
The ASCII table lists it as 0x2A, Unicode calls it U+002A, but everyday humans see a tiny five-pointed shape that can unlock voicemail, censor expletives, or mark required form fields. Mislabel it in code comments and the next contractor grep-ing for “star” will miss every authentication routine you wrote.
ASCII Origins and the 1963 Naming Split
Teletype engineers coined “asterisk” in 1963 because the symbol already existed on typewriter keyboards used for footnotes. The same committee shortened “figure shift” to “digit” and left the name “star” unofficial, assuming casual users would adopt it naturally.
Early BASIC interpreters echoed this duality: PRINT “*” produced a star, but the token list in the manual called it ASTERISK. That lexical trace still lives in Ruby’s .asterisk? method and Python’s str.isasterisk proposal that never left the PEP draft.
When Unix shipped in 1969, Ken Thompson kept the formal name out of kernel source; the file globbing code literally checks for 0x2A, yet the man page reads “star matching.” This silent inconsistency trained two generations of developers to toggle terms contextually.
Telephony: Why Asterisk® Became a Brand
Mark Spencer needed a trademarkable name for his open-source PBX in 1999; he filed “Asterisk” because the symbol already adorned every phone keypad. The USPTO granted it, so anyone writing about the software must include the ® on first reference or risk a cease-and-desist.
Inside a dial-plan, the symbol triggers wildcard pattern matching; outside the switch, marketers insist you call the project “Asterisk PBX” never “Star PBX.” This legal boundary forces technical writers to maintain a style sheet that distinguishes between the executable and the glyph.
Carriers submitting SIP headers still use “*” to request server features, but the IETF draft cautions against spelling it out as “star” lest a courtroom construe the document as infringing collateral. The result is a surreal standard: everyone sees a star, yet no RFC dares speak its casual name.
Command-Line Globbing and the 0x2A Byte
Shells expand “*” by reading directory entries directly, skipping stat() calls for speed. If you alias star to asterisk in documentation, newcomers literally type the word “asterisk” and wonder why bash returns “command not found.”
PowerShell sidesteps the lexicon war by using the wildcard term in help files, but the parser still expects 0x2A. This dual vocabulary forces cross-platform scripts to embed comment blocks that translate on the fly for Windows versus POSIX users.
Hidden Dot Files and the Double-Star
“**” emerged in zsh 1990 as a recursive glob, later adopted by bash 4.0 and Python’s pathlib. Calling it “double star” is safe; calling it “double asterisk” confuses Pythonistas who expect exponentiation.
Webpack’s glob-loader documentation once mixed both terms, causing a 47-comment GitHub thread that ended with a commit enforcing “double star” everywhere. The takeaway: pick one phrase per ecosystem and lock it in CI linting.
Regular Expressions: Greedy Star vs. Asterisk Quantifier
The regex token “*” is officially “asterisk quantifier” in the IEEE spec, yet every tutorial slide calls it “the star.” This mismatch produces Stack Overflow answers that fail to match when copy-pasted into grep –perl-regexp mode.
JavaScript’s unicode flag treats the symbol as a literal 0x2A, not punctuation, so /*/u matches only the glyph itself. If you search code for the string “star” you will miss every escaping backslash that shields the quantifier.
Atomic Grouping Saves You From the Catastrophic Backtrack
When a greedy star overruns a capture group, atomic grouping (?>.*) prevents exponential time without changing the glyph name. Document the fix by writing “star quantifier inside atomic group” so reviewers instantly see the pattern shape.
Password Masking UX: Black Star vs. White Star
iOS renders password dots as U+25CF (black circle), but Android used U+2605 (black star) until Material 3 switched to U+2022 (bullet). If your security white-paper screenshots an Android 11 login screen, calling the mask “asterisk” is technically false.
WCAG 2.2 recommends announcing “masked” to screen readers, yet NVDA still says “star” for any U+002A in a password field. Designers who swap the glyph for stylistic reasons must audit the accessibility tree or fail compliance audits.
Markdown and the Accidental Bullet
GitHub-flavored Markdown treats a leading “*” as a bullet, never as a literal star. Writers who paste ASCII art ships firing cannons watch them morph into unordered lists unless wrapped in code fences.
Obsidian’s live preview caches the AST node type, so toggling editor mode can flip a cosmetic star into a bullet and break alignment. The workaround is using the HTML entity * which renders identically but sidesteps the parser.
Database Full-Text Search: Wildstar vs. Asterisk Wildcard
MySQL’s FULLTEXT boolean mode demands “*” appended to the prefix, but the manual cautions it is “not a regular expression star.” Elasticsearch normalized this by calling the same token a “prefix wildcard,” freeing devs from lexical gymnastics.
PostgreSQL pg_trgm ignores the symbol unless you escape it with double quotes, so a user searching for “C*” to find “C++” receives zero rows until the query is rewritten to plain “C”. Document this edge case with a one-line comment: “trgm drops star; use ILIKE instead.”
Internationalization: The Star That Is Not Always Five-Pointed
Unicode offers U+2606 (white star), U+272F (pinwheel star), and U+1F31F (glowing star), each with distinct semantic mappings in CLDR annotations. A Chinese e-commerce site using U+1F31F for ratings will see screen readers on macOS speak “glowing star,” whereas NVDA on Windows says “yellow star,” altering perceived sentiment.
When you generate alt text, specify the exact code point so translators do not substitute a culturally unlucky four-pointed glyph. Failing this, Arabic RTL layouts may mirror the star, flipping your “rating badge” into a visual arrow that points away from the product image.
Kanji Radical 忄and the Look-Alike Trap
The Chinese radical 忄(related to heart) resembles a slanted star in some fonts; OCR engines misread it as 0x2A and break CSV imports. If your data pipeline ingests multilingual invoices, blacklist fonts that collapse the distinction or risk phantom asterisks in monetary columns.
Cryptography: The Star Cipher That Never Was
During WWII, the U.S. Signal Corps tested a toy cipher where each five-pointed star on a map represented a rotor setting. Archivists later scanned the forms and ran OCR; every star became an ASCII 0x2A, corrupting the decryption timetable until a curator re-typed by hand.
Modern HSM firmware uses “*” as a visual separator in key checksums, but the printed label omits the name to avoid language export restrictions. Field techs must know that the tiny star is not a bullet placeholder but part of the SHA-256 fingerprint.
Legal Contracts: Star as Signature Substitute
Some U.S. states let illiterate signers mark “*” on deeds, but the statute spells out “asterisk” to deter forgery by stylized stars. A 2019 Florida case voided a will because the notary wrote “star” in the jurat, creating a fatal mismatch with the statutory term.
Smart-contract platforms encode the same logic: Solidity comments warn that EIP-191 personal messages must hash the exact byte 0x2A, not a Unicode star. Litigants who paste a fancy glyph into MetaMask sign a different hash and lose custody disputes.
SEO and the Unsearchable Symbol
Google strips “*” from queries, treating it as a wildcard operator, so a punk band named “* *” is effectively invisible. Their workaround was registering the domain “asteriskasterisk.com” and 301-redirecting to “starstarmusic.com,” capturing both keyword variants without duplicate content.
Schema.org review markup accepts “*” in the ratingValue field, but Google’s validator warns if you use the word “star” in the same object. Separate the concerns: keep the symbol for machines, write “star” only in human-visible text, and you dodge Rich Snippet penalties.
Accessibility: Braille and the Six-Dot Dilemma
Braille ASCII assigns “*” to dot-5 plus dot-2, a pattern that also means “in” in Grade-2 contractions. Screen readers switch pronunciation based on surrounding spaces, so “5*3” becomes “five multiplied by three” while “item*” is read “item asterisk.”
NVDA’s speech dictionary lets users remap the word “star” to “asterisk,” but doing so breaks emoji readings where “⭐” should stay “star.” The safest config is to leave the symbol untouched and educate content authors to write surrounding text that disambiguates intent.
Printing and Typography: Ink Spread Makes Stars Fat
At 6 pt size on newsprint, a 5-point star fills in and resembles a solid circle; proofreaders mark the defect with the same symbol, creating recursive confusion. Designers compensate by switching to a seven-point star or enlarging the counter to 15 % of the glyph width.
Variable fonts interpolate the star shape between rounded and straight terminals; on OLED screens the angular version traps off-axis light and appears brighter, nudging users toward higher engagement in A/B tests.
Future-Proofing Your Style Guide
Adopt a three-tier rule: call it “asterisk” in code, “star” in UI copy, and use the Unicode name in data schemas. Publish the rule in a single living page, version it in Git, and let CI fail a pull request if the wrong string appears in the wrong tier.
Keep a running lookup table that maps every occurrence of 0x2A to its contextual label; a one-line pre-commit hook can grep for violations faster than any human reviewer. Your reward is a codebase where no one wastes an hour asking, “Do I grep star or asterisk?”—they already know the answer is both, but never at the same time.