Contextual Letter Forms
Arabic letters change form by position. The selected font and shaping stack must apply contextual substitutions consistently.
Comparison
Arabic Image Rendering
Mirqam vs Puppeteer and Cloudinary
Modern tools can all participate in an Arabic rendering workflow. The useful comparison is who owns fonts, shaping, browser lifecycle, determinism, and validation.
Implementation comparison
Mirqam vs Generic Image Tools
| Criterion | Mirqam | Puppeteer / Chrome | Cloudinary |
|---|---|---|---|
| RTL layout | Arabic-first template engine | Browser CSS and layout when configured | Text overlay behavior to validate per design |
| Diacritics | RAQM-backed positioning with golden tests | Chrome shaping with the loaded font | Validate the chosen font and transformation output |
| OpenType shaping | Owned server-side shaping stack | Chrome shaping stack | Managed renderer; verify required features |
| Custom fonts | Upload TTF/OTF in the product | Load or install fonts in the browser environment | Upload authenticated TTF/OTF/WOFF2 assets |
| Deterministic output | Pinned renderer and fonts | Pin browser, fonts, OS image, and CSS | Managed service plus versioned transformations |
| Runtime profile | Hosted API render without a browser capture lifecycle | Browser launch/page/capture lifecycle to manage | Remote transformation with CDN-cached derived assets |
| Integration model | POST JSON and binary image response | Custom HTML, browser code, and capture | Transformation URLs or SDK calls |
The technical problem
Why Arabic Rendering Needs an Owned Pipeline
Diacritics Positioning
Harakat require precise mark positioning through font tables and the shaping engine, then visual verification with the target font.
Ligatures & Kashida
Ligatures and elongation rely on OpenType substitutions and positioning; requirements vary by font and design.
Bidirectional Text
Mixing Arabic, Latin text, and numbers requires correct Unicode bidirectional handling at every layout boundary.
Font Provisioning
Every environment must load the intended Arabic font and avoid silent fallback to a different system font.
Deployment Consistency
Browser pipelines can be reproducible when versions, fonts, CSS, and the OS image are pinned. Mirqam owns those rendering dependencies as one service.
Frequently Asked Questions
Can Puppeteer render Arabic correctly?
Yes. Modern Chrome can shape Arabic correctly when the page loads the intended fonts and CSS. The engineering work is pinning the browser, fonts, dependencies, and capture lifecycle so output stays reproducible.
Can Cloudinary handle Arabic text overlays?
Cloudinary supports text overlays, variables, and uploaded custom fonts. Teams should validate shaping and diacritics with their exact Arabic font and transformation; Mirqam owns that Arabic-focused rendering path directly.
What makes Arabic text rendering demanding?
Arabic is cursive: letter forms change by context, diacritics require precise mark positioning, and mixed-direction text needs correct BiDi handling. A production pipeline must control fonts, shaping, layout, and output tests together.
Does Mirqam support custom Arabic fonts?
Yes. Upload TTF or OTF fonts and use them in templates. Mirqam applies the server-side shaping stack consistently and keeps rendering independent of a browser screenshot.
Is Mirqam always faster than Puppeteer or Cloudinary?
Performance depends on deployment, network, browser reuse, template complexity, and caching. Mirqam avoids a browser capture lifecycle; benchmark all options with your own payloads and throughput targets.
Own the Arabic Rendering Path
Choose the workflow whose fonts, dependencies, output tests, and operational profile match your production requirements.