Where JUZZ content comes from

Quran structure and counting

JUZZ contains 114 surahs and uses the 6,236-ayah Kufic counting convention for browsing, progress, highlighting, juz ranges, and generated public pages. Juz boundaries are based on the canonical 30-part division represented in the app.

Some Riwayah recordings use a different ayah-numbering convention for specific surahs. JUZZ keeps the displayed interface on the 6,236-ayah convention and does not force an incompatible timing file onto those recordings.

Arabic verse text

The expanded player requests Uthmani Arabic text from the AlQuran.Cloud API using its quran-uthmani edition. Arabic copy actions use Arabic text fields, not presentation glyph codes.

The Read page also uses Quran.com page and word data through JUZZ’s same-origin /api/mushaf-page and /api/mushaf-surah endpoints so browser-facing code does not call external Quran APIs directly.

Basmala handling

Surah pages follow one shared normalization rule. In Al-Fatihah, the basmala remains Ayah 1, matching the source edition. In At-Tawbah, no basmala is rendered. In every other surah, one standalone basmala line appears before Ayah 1 and any duplicated basmala prefix is removed from the Ayah 1 text itself. Byte-order marks (U+FEFF) are stripped from imported text. No wording, punctuation, diacritic, or verse order is changed beyond that.

The same rule is applied to server-rendered pages, the player, Read mode (Mushaf, Continuous, and Words views), exports, and API responses through a single shared function.

Mushaf scripts and layouts

Read mode offers verified Mushaf text/layout options backed by Quran.com page data and local or permitted fonts: Madinah QCF V2, Uthmani V1, Tajweed Color, Uthmanic Hafs, KFGQPC Hafs, and IndoPak. The Surah header cartouches use a local QCF Surah Header font.

JUZZ does not label Hafs text as Warsh, Qalun, or Duri text. Riwayah audio variants are available in the reciter catalogue, but true non-Hafs Mushaf text variants will only be exposed when the underlying text/page source is verified for that Riwayah.

English translation

The player requests the Sahih International English translation from AlQuran.Cloud using the en.sahih edition. A translation is an interpretation of meaning and is not the Quran’s Arabic text.

Recitation audio

Ayah-by-ayah MP3 recitation is delivered from EveryAyah. Full-surah MP3 recordings are delivered primarily from the MP3Quran servers; surahs missing from MP3Quran for a given reciter may be served from Way2Quran or other listed fallback archives when a recording has been verified. JUZZ currently exposes 75 reciters.

The catalogue includes Hafs reciters and Riwayah reciters such as Warsh, Qalun, and Duri where complete, reliable full-surah sources are available. Each reciter page and listen/share page identifies the selected reciter and opens the app with that reciter.

Timing and highlighting

Word-level timing data comes from the Quran.com audio API where available. Ayah-boundary timing data can come from EveryAyah timing files, MP3Quran ayah timing endpoints, or locally generated timing maps created from reciter audio. Timing files are stored as local JSON maps when they exactly match the app’s displayed ayah count for that surah.

For Riwayah recordings whose source timing uses a different ayah-numbering convention, JUZZ intentionally omits the incompatible local map and falls back instead of showing a false exact highlight. Displayed durations and fallback highlights remain approximate and can vary by reciter, style, speed, and recording.

Recitation durations

Listen pages and the “how long to recite” answers on surah pages use real recording durations derived from ayah timing maps: the final ayah boundary of a recording is treated as its end, the same value the player uses for progress. Durations are shown only when a verified timing map exists for that reciter and surah; otherwise the page says so plainly instead of guessing.

Reciter portraits

Portraits were discovered from public reciter profiles, search results, and Wikimedia-style public sources, normalized to local 320×320 WebP assets where possible, and used for identification. Portrait rights remain with their respective owners. A source ledger is maintained with the project when a portrait is added.

Generated pages and metadata

Public surah, juz, reciter, and listen pages are generated from the local catalogue and Quran structure data. Sitemaps, LLM reference files, Open Graph metadata, and reciter counts are regenerated when the catalogue changes.

Surah guides and hadith sourcing

Each surah page carries short answer-first sections: what the surah is about, how long it takes to recite, and — only where a reliable source supports it — why it is recited before sleep. Hadith claims cite the collection and, where known, the grading (for example Sunan at-Tirmidhi with his hasan grading, or Sahih al-Bukhari). Devotional traditions are presented as practices some Muslims follow, never as universal rulings, and claims with unclear sourcing are omitted rather than repeated.

Third-party services and non-affiliation

JUZZ is an independent interface and is not endorsed by or affiliated with AlQuran.Cloud, Quran.com, EveryAyah, MP3Quran, Way2Quran, or the reciters. Third-party providers can change availability, URLs, audio quality, or rate limits outside JUZZ’s control.

Corrections

JUZZ distinguishes source data from interface estimates and does not invent missing Quran values. If you suspect an error, verify it against an authoritative Mushaf and the named upstream provider, then contact support with the surah, ayah, reciter, mode, device/browser, and the source you used to compare it.