Learn the many ways to use custom fonts in Power Apps
summary
Power Apps ships about 14 built‑in fonts, so three proven workarounds are shown: local device fallback — reference a font name in the Font property so Windows users see it but mobile or mac users don’t; SVG base64 embedded image — convert a TTF/OTF to base64 (via a font transformer) and render text as an SVG image so it looks identical on every device; PCF that injects Google Fonts — a PowerApps Component Framework component requests a Google Fonts stylesheet into the DOM, works web and mobile, lives on GitHub, and editing raises a one‑time “unsafe code” warning.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 1:56The custom font challenge
- 3:31Method 1: Local system fonts
- 11:30Method 2: SVG font embedding
- 23:58Method 3: PowerApps Component
- 36:22Method comparisons and recap
- 40:55Book promotion and closing
related talks
43mCracking the Code
34m글로벌 서비스를 하게 되면 겪게 될 폰트 렌더링 문제
34mMake Your SwiftUI Design System Portable with Swift Packages
45mUsing Power Platform to accelerate full-stack software development
44mMobile: How Style Xamarin Forms App
26mUniversal Components & Deterministic Rendering
13mCustom CSS is the path to inconsistent UI
31mTailwind CSS: It looks awful, and it works