Website Navigation • Theme • Translation
Download KJV Bible Search

Download KJV Bible Search on Google Play:
https://play.google.com/store/apps/details?id=com.kjv.biblesearch&pcampaignid=web_share

Support

Last Updated: 26 August 2026

Welcome to the official Support page for KJV Bible Search. This page covers the current four-product ecosystem and the latest downloadable security-hardened releases.

  • KJV Bible Search — Website Version (browser-based Website + 1,189 static Full Chapter View pages)
  • KJV Bible Search — Android App (Google Play; offline + online operation)
  • KJV Bible Search — WordPress Plugin v1.5.3 Security Hardened
  • KJV Bible Search — Universal HTML + Installable PWA v1.5.4 Security Hardened

For the two downloadable server packages, use only the current official ZIP files from KJVBibleSearch.net:

📘 Product Overview

Website Version

  • Unified online KJV Bible JSON search.
  • 1,189 static HTML Full Chapter View pages.
  • Nine complete Prophetic Series books/pages.
  • Built-in Text-To-Speech where supported.
  • Keyword highlighting and real-time verse highlighting.
  • Book → Chapter → Verse navigation.
  • Browser-provided translation workflow when the user chooses to use it.

Android App — Google Play

  • Built-in offline KJV Bible engine.
  • Offline full-Bible search and navigation.
  • Offline Text-To-Speech for Bible chapters and supported Prophetic Series content.
  • Offline and online real-time verse highlighting.
  • Online access to KJVBibleSearch.net chapter and book pages when connected.
  • No KJV Bible Search advertising analytics or behavioral tracking.

WordPress Plugin v1.5.3 Security Hardened

  • Bundled kjv_full.json KJV Bible database — no remote Bible API is required for core Bible search.
  • Instant full-Bible search, keyword highlighting, TTS, real-time verse highlighting, Copy/Share and navigation.
  • WordPress shortcode integration.
  • RSA-3072/SHA-256 signed integrity manifest.
  • Bundled public verification key; the private release-signing key is never included in the public ZIP.
  • SHA-256 protected-file verification and explicit integrity states.
  • WordPress Site Health integrity status and administrator tamper warnings.
  • Scheduled integrity verification and unexpected PHP-file detection.
  • Apache/LiteSpeed .htaccess and Microsoft IIS web.config hardening.
  • Read-only ZIP permission metadata where the destination server/filesystem preserves it.

Universal HTML + Installable PWA v1.5.4 Security Hardened

  • One Universal product with two deployment methods: standalone HTML/CSS/JavaScript and installable PWA.
  • Packaged KJV Bible/application resources — no remote Bible API is required for core Bible search.
  • Full-Bible search, TTS, highlighting, Copy/Share and Book → Chapter → Verse navigation.
  • Installable Progressive Web App on supported browsers/devices.
  • Offline operation after the required application/Bible resources have been successfully cached.
  • RSA-3072/SHA-256 signed release manifest and bundled public verification key.
  • SHA-256 integrity verification and browser-accessible security-status page.
  • Subresource Integrity (SRI) for core CSS/JavaScript.
  • Service-worker verification before registration.
  • Apache/LiteSpeed .htaccess and Microsoft IIS web.config hardening.
  • No phone-home integrity tracking or remote verification dependency.

⬇️ Installation Help

Install the WordPress Plugin v1.5.3

  1. Download kjv-bible-search.zip.
  2. In WordPress, go to Plugins → Add New → Upload Plugin.
  3. Upload the ZIP without manually extracting or rearranging its internal files.
  4. Activate KJV Bible Search.
  5. Add the [kjv_bible_search] shortcode to the page/post where you want the Bible Search interface.
  6. Open the plugin status/settings area and confirm the integrity result is VERIFIED.

Optional shortcode controls supported by the current release include:

  • [kjv_bible_search show_prophetic_series="no"]
  • [kjv_bible_search show_app_link="no"]
  • [kjv_bible_search show_prophetic_series="no" show_app_link="no"]

Install the Universal v1.5.4 Package

  1. Download kjv-bible-search-universal.zip.
  2. Extract the ZIP on your computer or server.
  3. Upload the complete extracted package to the intended web root or subdirectory.
  4. Do not omit the manifest, service worker, integrity files, public key, icons, JSON Bible data, CSS or JavaScript files.
  5. Open the Universal application in a supported browser.
  6. Open security-status.html and confirm local integrity verification.
  7. For PWA installation, serve the files over HTTPS or another browser-supported secure context.

❓ Frequently Asked Questions

Does KJV Bible Search collect personal data?

KJV Bible Search does not operate KJV Bible Search user accounts, advertising profiles or behavioral analytics profiles. Normal web-server, browser, device, app-store, WordPress, CDN or hosting logs/caches may exist independently of the KJV Bible Search application and are controlled by the relevant provider or site administrator. See the Privacy Policy for the controlling privacy wording.

How does translation work?

KJV Bible Search does not integrate Google Translate API, LibreTranslate, or another translation API into its own application code. If you choose browser-provided translation, that process is controlled by your browser/browser provider and is subject to that provider's privacy practices and technical behavior.

Why is KJV Bible Search ad-free?

The KJV Bible Search interface is designed as an ad-free Bible-search experience without KJV Bible Search behavioral advertising or analytics profiling.

What works offline?

  • Android App: the built-in offline Bible engine, search, navigation, TTS and supported highlighting/content are designed for offline operation.
  • Website Version: primarily an online browser experience; ordinary browser caching does not make the complete website an officially supported offline edition.
  • WordPress Plugin v1.5.3: the Bible database is bundled locally with the plugin, but visitors normally access the plugin through the WordPress website/server. It does not require the KJVBibleSearch.net Bible server for core search.
  • Universal v1.5.4: supports installable PWA/offline operation after required resources are successfully cached in a supported browser/device.

Can the hardened ZIP files still be modified?

The packages are security hardened, cryptographically signed and tamper-evident, but they cannot be made literally impossible for a hosting account owner, root administrator or filesystem owner to alter. Read-only ZIP permission metadata may also be changed or discarded by the destination operating system, archive tool, WordPress installer or hosting filesystem.

Should I upload the private signing key?

No. The private release-signing key must never be placed in a public web directory, inside either downloadable ZIP, in WordPress Media Library, GitHub, or any public server location. Only the bundled public verification key belongs in the downloadable packages.

🔐 Integrity & Security Status Help

WordPress Integrity States

  • VERIFIED: protected files match the official signed release data.
  • MODIFIED: one or more protected files no longer match their expected SHA-256 values.
  • MISSING: a protected release file is absent.
  • UNEXPECTED FILE: an unexpected executable/PHP file was detected in the protected plugin area.
  • INVALID MANIFEST: the integrity manifest cannot be accepted as valid release metadata.
  • SIGNATURE FAILURE: the signed release manifest does not verify against the bundled public key.

If a WordPress installation reports anything other than VERIFIED, first compare the installation with a freshly downloaded official kjv-bible-search.zip. If you did not intentionally modify the plugin, replace it with a clean official copy and investigate the server/hosting account for unauthorized changes.

Universal Integrity Verification

  • Open security-status.html from the deployed Universal package.
  • Confirm that the signed manifest and protected-file hashes verify successfully.
  • If SRI blocks a CSS/JavaScript asset, do not simply remove the integrity attribute; determine why the deployed file differs from the signed official release.
  • If the service worker will not register, confirm that its integrity verification passes first.

🛠 Troubleshooting

Android App Issues

  • Restart the app or device.
  • Ensure sufficient device storage is available.
  • Check battery-optimization settings if background/audio behavior is restricted.
  • Check internet access only for features that require the online KJVBibleSearch.net environment.
  • For Google Play installation/update problems, use the Google Play Store's own account/device troubleshooting.

Website Version Issues

  • Reload the page and clear stale browser cache if necessary.
  • Ensure JavaScript is enabled for interactive search, TTS and highlighting features.
  • Try a current version of Chrome, Edge, Safari or another supported modern browser.
  • If a specific Full Chapter View page fails, verify the exact URL and try the chapter page directly.

WordPress Plugin v1.5.3 Issues

  • Confirm you installed the current official kjv-bible-search.zip and not an older ZIP.
  • Confirm the plugin activates without PHP errors on the site's current WordPress/PHP environment.
  • Check for theme, optimization/minification, security-plugin, CDN or caching conflicts.
  • Confirm the bundled data/kjv_full.json exists and is readable.
  • The plugin does not require an external KJVBibleSearch.net Bible API for its core search.
  • If direct JSON access is restricted by the host, the plugin's read-only WordPress fallback can deliver the bundled Bible data.
  • Check the plugin integrity/status page and WordPress Site Health for tamper or missing-file warnings.
  • If integrity fails unexpectedly, reinstall from a freshly downloaded official ZIP rather than editing the manifest/hashes to suppress the warning.
  • If the host discards read-only permissions during extraction, that does not by itself mean the package is invalid; use the cryptographic integrity status to verify the deployed files.

Universal v1.5.4 Issues

  • Confirm the complete extracted package was uploaded, including hidden files such as .htaccess where your upload method/server uses them.
  • Do not upload only index.html; the CSS, JavaScript, JSON, icons, PWA files, public key and integrity files are all part of the complete package.
  • Confirm JavaScript is enabled.
  • Confirm the relative file paths still match the package structure.
  • For PWA installation/service-worker use, deploy over HTTPS and ensure the browser permits service workers.
  • If offline mode does not work yet, load the application online first so the required resources can be cached successfully.
  • Check browser storage/quota settings if caching fails.
  • Open security-status.html to verify the signed package.
  • If SRI reports a mismatch, restore the official file rather than removing the integrity protection.
  • If the service worker fails integrity verification, restore the official service-worker.js from a clean download.
  • The Universal release does not require retrieving its Bible database from KJVBibleSearch.net for core search.

Apache/LiteSpeed or IIS Server Rules

  • Apache/LiteSpeed deployments can use the packaged .htaccess rules where permitted by the host.
  • Microsoft IIS deployments can use the packaged web.config rules where permitted.
  • If your hosting provider does not honor these files, use the equivalent server configuration available in that hosting environment.
  • Do not assume server-level rules alone make the files unchangeable; signed integrity verification remains the authoritative tamper-evidence layer.

📩 Contact Support

If you need help, have feedback, or want to report an issue, please contact:

ALPHA & OMEGA LIMITED
Email: Contact@kjvbiblesearch.net
Website: https://kjvbiblesearch.net

When reporting a WordPress or Universal problem, include the product/version, hosting/server type, browser/WordPress version where relevant, exact integrity status/error message, and whether the problem also occurs after reinstalling a fresh official release.

🔗 Helpful Links