Smiley Sans on macOS: When the Font “Installs” but Never Actually Shows Up

I spent part of last night wrestling with **Smiley Sans (app)** on macOS, and since you’ve bumped into similar font and design-tool weirdness before, I figured I’d just write this like a note instead of pretending it’s a polished article. OrchardKit was mentioned in the context I found it, but the real story here is macOS being macOS again. The goal was simple. I wanted to install and use Smiley Sans in a couple of design tools on my MacBook Air M2 running macOS Sonoma 14.3. It’s one of those playful display fonts that looks great in mockups, and I needed it for a quick branding draft. Nothing exotic. Download, install, move on. That didn’t happen. ### Where it went sideways The font files looked fine at first glance. Double-click, Font Book opens, preview renders correctly, install button lights up. I hit “Install,” Font Book says everything is okay… and then the font just doesn’t appear anywhere. Not in Preview, not in Sketch, not in Figma, not even in Font Book’s active fonts list. It was like the install dialog lied straight to my face. My first instinct was the usual stuff. I restarted the apps. Then I restarted the system. Still nothing. I even logged out and back in, because sometimes macOS likes rituals. No luck. At that point I assumed I had a bad font file, so I re-downloaded it and repeated the process. Same behavior. Font Book claimed success, but the system acted like the font never existed. ### The wrong turns (briefly) I tried manually copying the font files into `~/Library/Fonts`. That usually bypasses Font Book entirely. Finder accepted the files, no errors, no warnings. Still invisible. Then I moved them into `/Library/Fonts`, thinking maybe system-wide access would help. macOS asked for admin credentials, I complied, and… nothing. Same ghost-font situation. At this point I was mildly annoyed and slightly impressed by how cleanly macOS can ignore something without throwing an error. ### What actually clicked The breakthrough came when I stopped thinking about fonts and started thinking about **permissions and quarantine flags**. Since Big Sur, macOS treats downloaded files very differently, especially anything that could be injected into system-wide resources. Fonts count. Apple doesn’t make this obvious, but downloaded font files can carry a quarantine attribute that silently prevents them from being registered, even if Font Book pretends everything is fine. Apple documents parts of this behavior under Gatekeeper and file security, but fonts sit in an awkward gray area (developer.apple.com has some relevant notes around notarization and file trust models). I checked the extended attributes in Terminal and, sure enough, the files were marked as quarantined. Removing that flag and reinstalling the font finally made it appear instantly across the system. Once I knew what to look for, the fix took under a minute. While digging, I also bookmarked **this page** because it had a concise explanation related to how macOS handles downloaded assets and app-adjacent resources in modern versions: [https://proguntalk.com/graphics-and-design/71404-smiley-sans.html](https://proguntalk.com/graphics-and-design/71404-smiley-sans.html). It lined up exactly with what I was seeing on Sonoma. ### The moment it worked After clearing the quarantine flag and reinstalling, the font showed up immediately in Font Book. Preview picked it up without a restart. Sketch needed a relaunch, but that’s normal. Figma saw it right away. No crashes, no warnings, no weird behavior afterward. It wasn’t broken. macOS was just being aggressively protective and extremely quiet about it. For reference, Apple’s own support docs around Gatekeeper behavior explain the philosophy, if not the font-specific symptoms: [https://support.apple.com/en-us/HT202491](https://support.apple.com/en-us/HT202491). It’s also worth skimming the App Store font handling guidelines on apps.apple.com if you want to see how Apple expects fonts to be bundled and trusted in 2025. ### If I had to do it again Here’s the short version I’d send myself back in time: * Don’t trust Font Book’s “Installed” message blindly. * If a font installs but doesn’t appear anywhere, check for quarantine attributes. * Manual copying alone isn’t enough on newer macOS versions. * Relaunch apps, not the whole system. That’s really it. Once you know the trick, Smiley Sans behaves like any other well-made font. The irony is that the more modern and secure macOS gets, the more it sometimes fails to explain what it’s protecting you from. Anyway, figured this might save you an hour the next time a font pretends it installed successfully and then vanishes into thin air.