Font Pairing / Designer Preview
Cactus Classical Serif has a IBM Plex Sans Arabic character, while Modern, Clean brings a Clean, Professional role to the page. Their difference creates hierarchy without requiring heavy decoration or extra visual effects.
The strongest use of Cactus Classical Serif is often in display moments, where its personality can be seen quickly. IBM Plex Sans Arabic then gives paragraphs and interface copy a steadier rhythm.
Typography Playground
Change the type scale, weights, spacing and sample copy to see how the pairing behaves in a real layout.
Typography Specimen
From headlines and paragraphs to navigation, buttons, captions and quotes, this specimen shows how the two typefaces can build a complete visual language.
Cactus Classical Serif × IBM Plex Sans Arabic / type relationship
Place Cactus Classical Serif where readers should look first and IBM Plex Sans Arabic where they need to slow down and absorb information. The result is a practical hierarchy that remains recognizably tied to the same pairing.
Cactus Classical Serif and IBM Plex Sans Arabic do not need to compete. Their roles become clearer when the first face is reserved for headlines and statements while the second handles paragraphs, labels and secondary information.
Read the story →For identity work, Cactus Classical Serif can become the recognizable headline voice while IBM Plex Sans Arabic supplies consistency across supporting applications.
“Use Cactus Classical Serif to attract attention; use IBM Plex Sans Arabic to keep it.”— Design principle / 2026
Real-world templates
Use practical layouts to judge the relationship between the heading and body faces before you commit to a design direction.
The hierarchy here is intentionally simple: Cactus Classical Serif takes the prominent role and IBM Plex Sans Arabic handles the supporting message so the layout stays expressive without becoming difficult to scan.
Explore this pairing →Cactus Classical Serif gives the headline a distinct presence, while IBM Plex Sans Arabic makes the supporting message easier to navigate.
Use Cactus Classical Serif for the project voice and IBM Plex Sans Arabic for the details that help visitors understand the work.
A confident headline face can give a brand a signature. A calmer body face keeps the system useful across packaging, web and editorial content.
Explore the collectionA simple hierarchy that lets Cactus Classical Serif create the hook and IBM Plex Sans Arabic carry the supporting thought.
Pairing guide
The relationship between Cactus Classical Serif and IBM Plex Sans Arabic is built around role separation: Cactus Classical Serif can attract attention, while IBM Plex Sans Arabic keeps supporting information clear across editorial layouts, portfolios, brand pages and digital content.
Modern, Clean paired with Clean, Professional creates a balanced starting point. The combination becomes more convincing when Cactus Classical Serif handles the strongest moments and IBM Plex Sans Arabic carries the longer reading passages.
This pairing is especially suitable for editorial layouts, portfolios, brand pages and digital content. Start with a clear heading-to-body hierarchy, then adjust size, weight and spacing to match the project.
Keep Cactus Classical Serif visually distinct from IBM Plex Sans Arabic rather than matching their sizes too closely. A noticeable hierarchy helps the pairing communicate structure without making the page feel fragmented.
Test Cactus Classical Serif in headlines, navigation or key statements and IBM Plex Sans Arabic in paragraphs, descriptions and metadata. Check the relationship at both large display sizes and comfortable reading sizes.
Frequently asked questions
Cactus Classical Serif and IBM Plex Sans Arabic currently score 69.7/100, classified as Usable match. The score is a design-oriented starting point; use the live preview to confirm the visual result for your project.
Cactus Classical Serif is assigned the Heading role in this pairing. Its job is to create the strongest visual entry point, while IBM Plex Sans Arabic supports the body and secondary information.
IBM Plex Sans Arabic is assigned the Body role. Use it for paragraphs, descriptions, captions and other text that needs a steady reading rhythm.
The pairing is suited to editorial layouts, portfolios, brand pages and digital content. Its usefulness comes from keeping the two typefaces in complementary roles rather than asking them to perform identically.
Start with a clear size and weight contrast, then tune line-height and letter-spacing. Compare the pairing in headlines, long-form text and interface elements before finalizing the system.
Complete pairing experience
Modern, Clean paired with Clean, Professional creates a balanced starting point. editorial layouts, portfolios, brand pages and digital content.
Use Cactus Classical Serif for the primary role and IBM Plex Sans Arabic for supporting content, then refine sizes, weights and spacing for your project.
h1, h2, h3 { font-family: 'Cactus Classical Serif', Arial, sans-serif; }
body, p { font-family: 'IBM Plex Sans Arabic', Arial, sans-serif; }Usable match
A weighted assessment of contrast, harmony, readability, style, weight balance, use case and popularity.
Good confidence: most of the signals used by the engine are well supported.
Designer read
Weight Balance is excellent. The overall score combines all seven signals using their published weights.
Measures whether the two fonts create enough visual difference to establish hierarchy without feeling disconnected.
Measures how naturally the two typefaces relate in proportion, character and family combination.
Measures how suitable the selected body font is for comfortable reading alongside the heading font.
Measures whether the personalities of the two fonts support the same visual direction.
Measures the balance of typographic thickness and hierarchy between heading and body roles.
Measures how practical the pairing is for common design contexts such as websites, editorial layouts and branding.
Uses available source popularity data as a small supporting signal; it is never the main reason a pair is recommended.
The overall score is a weighted average of seven design signals. Each signal is scored from 0–100 and multiplied by its contribution weight. Confidence is separate: it describes the strength of the evidence behind those signals.