Choosing a block

Eight packages, each answering a different question. The fastest way to choose is to start from what you are trying to put on a screen, not from the package names.

Start from your task

You want to…Use
Show Qur’an text you control the layout ofQuran Text
Show the printed page exactly as it appears in a muṣḥafQuran SVG
Make individual words tappableQuran SVG Elements
Do that on mobile, at speedQuran Engine
Colour the text by recitation ruleQuran Tajweed
Support more than one reading, or translate a referenceQiraat Ayah Map
Draw ayah markers, frames or surah headersQuran Assets
Share an ayah as an imageQuran PNG

The relationship that is easiest to get wrong

Quran SVG, Quran SVG Elements and Quran Engine are not three stages of one pipeline, and not a queue where the others eventually catch up. They trade coverage against how deeply you can address the page.

CoverageYou can address
Quran SVGEvery vectorised muṣḥaf, and growing by contributionAn ayah
Quran SVG ElementsOnly what has been splitA word, a mark — a letter, later
Quran EngineThose split muṣḥafs, on mobileThe same, fast
Coverage against addressing

Quran SVG is the archive, not a stepping stone. Splitting a muṣḥaf is hard, and not every one of them will ever be split.

Quran Engine exists because SVG does not perform on mobile. That is the reason to reach for it, not a benchmark.

Elements ships 604 whole displayable pages too. The difference is what you can address, never “pages versus parts”.

All eight, by role

Data

Pages & Assets

Rendering

Annotations

Guidance

What each one is not for

Each entry links to the sibling that does the job instead.

Quran Text
Qiraat Ayah Map
Quran SVG
  • Word-level interaction — these pages carry an ayah layer only. Where a mushaf has been split, use Quran SVG Elements
  • Mobile and native, where SVG stops performing. Use Quran Engine
  • Text you can search. Use Quran Text
Quran SVG Elements
  • Any mushaf that has not been split — splitting is hard, and not every mushaf will be. Use Quran SVG
  • Mobile and native, where SVG stops performing. Use Quran Engine
  • Tapping whole ayat, where an ayah polygon is simpler. Use Quran SVG
Quran Assets
Quran Engine
  • The web, where the split SVGs already work well. Use Quran SVG Elements
  • Just showing a page and tapping ayat — an SVG and a few lines of JavaScript do that. Use Quran SVG
Quran Tajweed
QuranTech
  • Runtime behaviour — it ships no code into your app.
  • Verified text. That is Quran Text