Sources.Attribution and source governance.
Hifzer now treats Qur'an content as a governed source stack, not just bundled files. This page shows what is active in the app today, which official/open datasets are easiest to add next, and the required attribution lines for the bundles already shipped.
Core text and metadata
Arabic text
Tanzil Uthmani export bundled locally for the canonical Arabic reader.
Metadata and transliteration
Surah/page metadata and transliteration are bundled locally and included in the same source set.
Translation bundle status
English - Saheeh International
VerifiedSource: Tanzil. Bundled from the Tanzil Saheeh International export with explicit attribution.
Bundled translations under review
6 pendingThese translations are live in the product, but their external source records are still being normalized into the registry before further source-backed expansion.
Seed build notes
These lines describe the seed inputs and local bundle mappings currently used to boot the Qur'an stack.
Canonical Arabic text: Tanzil Uthmani export (local file, no runtime fetch). Metadata (page/juz/hizb): provide local JSON mapping keyed by `surahNumber + ayahNumber`.
Tanzil
Best first source for locally bundled Qur'an text and metadata governance.
Setup
Direct download. No account or API key is required for the Arabic text export.
What it needs
- - Choose the export format you want to bundle locally.
- - Keep the Arabic text verbatim and preserve Tanzil attribution.
Best for
QuranEnc
Fastest source for broad multilingual coverage once each target translation is reviewed.
Setup
Public translations and API/docs are exposed without OAuth in the official developer entry points.
What it needs
- - Pick the translation/language dataset you want to bundle or sync.
- - Review the translation-specific policy before shipping it in product.
Best for
King Fahd Glorious Qur'an Printing Complex
Good accessibility and official-reference layer after the core text/translation stack is stable.
Setup
Official audio translation assets are available publicly, but integration is closer to asset ingestion than a modern JSON API.
What it needs
- - Select the translation-audio collection you want to support.
- - Package/cache the assets for the listening experience you want.
Best for
Quranic Arabic Corpus
High-value enrichment source once licensing is clarified for your commercial distribution.
Setup
Downloadable morphology and syntax data exist, but commercial use should be treated as legal-review-first.
What it needs
- - Provide a contact email for downloads.
- - Review corpus licensing and commercial-use assumptions before embedding it in product.
Best for
Quran.Foundation / Quran.com APIs
Most powerful long-term integration, but not the fastest source to land first.
Setup
Richest official API stack, but it requires approved access, client credentials, and OAuth2 flows.
What it needs
- - Request API access and receive client credentials.
- - Configure OAuth2 and redirect URLs for any user-linked flows.
Best for
Tanzil metadata header
Copied verbatim from the Tanzil quran-data.js metadata file header.
Quran Metadata (ver 1.0) Copyright (C) 2008-2009 Tanzil.info License: Creative Commons Attribution 3.0
English translation source
Sahih translation metadata and attribution for the bundled en.sahih text.
Quran Translation Name: Saheeh International Translator: Saheeh International Language: English ID: en.sahih Last Update: April 24, 2011 Source: Tanzil.net English translation: Saheeh International (en.sahih), sourced from Tanzil.net. Source URL: https://tanzil.net/trans/en.sahih Catalog/terms: https://tanzil.net/trans/