Developers

Quranic text, word-by-word data, translations, tafsirs, footnotes, search and audio metadata are served from our own database, through qurangallery.com/quran/api/quran. Nothing on a reading page depends on a third-party API being up.

It covers the complete Quran in six script variants, 150 translations, 23 tafsirs, and per-mushaf page and line positions for every word — plus the metadata for surahs, verses, juz and the other divisions. Responses follow the v4 response shape most Quran tooling already expects, so existing clients read them unchanged. Recitation audio itself is still streamed from QuranCDN.

Every endpoint below is served from our own corpus and takes the usual v4 query parameters (language, translations, words, page).

Key endpoints include:

• /chapters — List all 114 surahs with metadata
• /verses/by_chapter/:id — Get verses for a specific surah
• /search — Full-text search across translations
• /resources/recitations — Available reciters and audio files
• /resources/translations — Available translations in all languages

Quran Gallery is built with modern web technologies focused on performance and accessibility:

Frontend

SvelteKit 2 with Svelte 5, Tailwind CSS v4

Runtime

Node.js on a self-hosted VPS (adapter-node)

Database

PostgreSQL via Drizzle ORM

Internationalization

Paraglide JS — 7 languages including RTL

We believe in open collaboration for projects that serve the Muslim community. Contributions are welcome — whether it is fixing bugs, improving translations, adding features, or enhancing accessibility.

Quran Gallery runs as a monorepo of Node.js services, each serving a different part of the platform. Caddy routes requests by path prefix to the appropriate service on the VPS.

qurangallery.com (Gateway)  /quran   → Quran reader and study tools  /chat    → AI-powered Quran chat  /studio  → Islamic art studio  /hifz    → Memorization tracker  /adhkar  → Daily supplications  /blog    → Articles and guides

For technical questions, API issues, or collaboration inquiries, reach out at [email protected] or open an issue on GitHub.