Need to match your brand fonts inside Canva designs? This guide shows you precisely how to add font to Canva using the platform's built-in upload tools. The process works for Canva Pro users and takes only a few minutes once you have your font files ready.
Canva restricts custom font uploads to Pro, Team, and Enterprise accounts. You must have the actual font files in .ttf or .otf format saved on your computer. Free accounts cannot upload fonts, though they can still access Canva's built-in library. Make sure your fonts are licensed for commercial use if you plan to publish designs publicly.
Prepare your files in advance. Canva accepts up to 100 custom fonts per Brand Kit, so organize them by style (regular, bold, italic) before starting.
Log into your Canva account at canva.com. Click the three-dot menu in the top-right corner, then select "Brand Kit" from the dropdown. If you manage multiple brands, choose the correct Brand Kit first.
Scroll down inside Brand Kit until you reach the "Fonts" heading. Click the purple "Upload fonts" button directly beneath it. A file selection window will appear on your screen.
Navigate to the folder containing your .ttf or .otf files. Select one or multiple fonts at once, then click Open. Canva processes each file and adds it to your Brand Kit within seconds.
Open any existing or new design. Click on a text element, then open the font dropdown in the top toolbar. Your uploaded fonts now appear at the top of the list under "Brand fonts". Select the desired weight to update the text instantly.
No. Font uploads are only available through the desktop or web version of Canva. Use a computer browser for this task.
Custom fonts do not use your design storage quota. They remain available as long as your subscription stays active.
Uploaded fonts disappear from Brand Kit once the account reverts to free. Re-subscribe and re-upload the files to restore access.
Following these exact steps lets you add font to Canva and maintain consistent branding across every project. Keep your font files organized and test them in a sample design before using them in client work.
Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.
Compare YaST and cryptsetup for a new encrypted SLES data volume, choose LUKS1 or LUKS2, and verify unlock and mount behavior safely.
Create, refine, and verify a least-privilege AppArmor profile on SLES 15 SP7, with a clear note on SLES 16’s SELinux default.
Set up RMT on SLES 15, mirror entitled repositories, and verify HTTPS registration and package access from a test client.
Connect SLES 15 to AD with YaST’s SSSD-based logon management, then verify directory lookup, domain login, and Kerberos tickets.
Set up the right Live Patching path for SLES 16.0 or 15 SP7, apply eligible kernel fixes, and confirm what is active without confusing it with a reboot-required kernel update.
Load a custom SLES 15 kernel module without disabling Secure Boot. Match the running kernel, sign the .ko file, enroll a MOK key, and verify loading.
SLES 15 SP5 can migrate online to SP6, but each node must reboot. Use a tested rolling upgrade or blue-green cutover to keep workloads reachable.
Use SUSE’s supported STIG profile to scan SLES 15, test remediation, review remaining findings, and retain assessment evidence.
Trace a failed Cockpit connection through DNS, port 9090, the systemd socket, firewalld, TLS, and login settings using current SUSE guidance.
