Download

Download the TachiyomiAT-style Nayovi APK

Install the Android APK from tachiyomiat.com for readers coming from TachiyomiAT, Tachiyomi AT, Tachiyomi, or Mihon workflows, then activate hosted mode with a redeem code and start translating manga or manhwa chapters from the app.

Latest TachiyomiAT-style Android APK

Universal APK for Android devices. Download it directly from the official Nayovi backend if you searched for TachiyomiAT APK, Tachiyomi AT download, Tachiyomi download, or Mihon translation setup.

Android arm64 signed release 0.17.2064 MBSHA-256 verified
What hosted mode adds
Hosted mode moves payment, token credits, redeem codes, device binding, and server-side provider routing.
Pay for token packs on the public website.
Redeem against an app installation instead of a user account.
Run OCR and translation through the backend without shipping provider keys to the device.
Video demo
Watch the current Android app flow before installing the APK.
Trust

Use the official APK path

Readers, reviewers, and affiliates should evaluate Nayovi from the same official download, activation, pricing, and support flow.

Official source
Start from the owned Nayovi download page before installing, reviewing, or listing the APK anywhere else.
Review-ready evidence
Keep the APK hash, build label, pricing, support, privacy, terms, and responsible-use notes attached to every public mention.
Pending identity fields
Mark package, signing-certificate, and Android developer verification facts as owner-confirmation required until they are public.
Install

Install in three steps

Android may ask you to allow installation from your browser or file manager before opening the APK.

Download the APK
Use any APK button on this page to download the latest Nayovi Android build for TachiyomiAT, Tachiyomi, and Mihon-style readers.
Allow installation
If Android asks, allow installs from your browser or file manager.
Activate hosted mode
Open the app, enter your redeem code, and start translating chapters.

Ready to install?

This APK link always points to the latest uploaded Nayovi build for TachiyomiAT-style Android readers.

Download APK
Verification

Reviewer and directory checklist

Use this packet when evaluating Nayovi for Android app coverage, app-directory listing, affiliate review, or creator-platform feedback.

Official source links
Use tachiyomiat.com and nayovi.com for APK details, pricing, support, privacy, terms, and responsible-use notes.
Review access
Ask for a redeem code, screenshots, narrated demo context, and package metadata before publishing a hands-on review.
Usage boundary
Describe Nayovi as hosted OCR and translation support for owned, public-domain, official-sample, or permission-approved content.

Need review-code context?

Send editors to the support path for a test code and cite the translation workflow guide for the no-chapter-hosting policy.

Review workflow guideComic OCR checklist
Trust

Independent APK distribution checks

Android app reviewers, directory editors, and readers can use these checks before treating any Nayovi APK link as authoritative, especially as Android developer verification changes how independent APKs are evaluated.

Start from the owned domain
Use tachiyomiat.com or nayovi.com as the source of truth before installing or reviewing an APK from any directory listing.
Match the published hash
Compare the SHA-256 value on this page with the downloaded file before citing, mirroring, or reviewing the build.
Keep support and policy links attached
A trustworthy listing should include support, pricing, privacy, terms, and the responsible translation workflow guide.
Record signing and verification status
Reviewers should keep the APK hash, signing-certificate notes, package name, and Android developer verification status with the listing packet.
Separate file hash from certificate identity
Record both the downloaded file SHA-256 and the signing-certificate SHA-256 fingerprint so readers can verify the exact file and the developer identity used for updates.

Nayovi is distributed as an official Android APK with hosted OCR and AI translation services. It should not be presented as an unaffiliated mirror, modded reader, chapter source, or replacement for publisher permission.

If a reviewer or app directory is preparing coverage for the 2026 Android developer verification rollout, cite this page as the source for current APK metadata and note any missing package-name, signing-certificate, or verification details as pending rather than guessing.

If a directory, forum, or review page cannot preserve these source-of-truth details, use the official download page instead of creating a separate listing.

APK metadata

Source-of-truth app details

Directory editors and Android reviewers can use these details to verify that a listing points back to the official Nayovi APK instead of an unsupported mirror.

File namenayovi-latest.apk
BuildAndroid arm64 signed release 0.17.20
APK size64 MB
SHA-2563ca6d69973da325f8ec03ef1c71d7cd8f4b63b8958498ef7bb8633cc9dc62bef
File integrity
Compare the downloaded APK file SHA-256 against the value on this page before publishing screenshots, mirrors, or installation instructions.
Signing certificate
Use Android signing tools or Play Console certificate details to record the app signing certificate SHA-256 fingerprint when it is available from the release owner.
Package identity
Keep the package name, build label, filename, APK size, and signing-certificate note together so future updates can be matched to the same official app.
Pending fields
If package name, certificate fingerprint, Play Console developer verification, or store metadata is not confirmed yet, mark it pending instead of guessing.

A correct listing should name Nayovi as an Android APK with hosted OCR and AI translation support, then send install, pricing, support, privacy, terms, and responsible-use questions back to tachiyomiat.com or nayovi.com.

Avoid listings that present the APK as an unaffiliated mirror or imply that Nayovi hosts manga, manhwa, or manhua chapters.

Directories

When a listing is acceptable

Use this filter before submitting Nayovi to AI-tool, APK, startup, or app-review directories.

Preserve the source of truth
A directory profile should link to the official download page, pricing, support, privacy, terms, and OCR checklist instead of hiding users behind a mirror page.
Avoid reciprocal-link gates
Skip listings that require dofollow backlinks, paid placement, review swaps, or homepage badges as the condition for indexing Nayovi.
Represent pricing accurately
Use free trial, redeem-code access, and paid token plans language; do not label Nayovi as a forever-free open-source app unless that becomes true.
Release proof

What reviewers should ask for before publishing

Use this release packet when a directory, newsletter, app reviewer, or partner needs evidence beyond a download button.

Package ownershipConfirm the package name, release owner, and official download URL before citing any third-party APK page.
Signing evidenceAttach the SHA-256 hash and signing-certificate fingerprint when the release packet exposes them.
Verification statusState whether Android developer verification is complete, pending, or not applicable instead of leaving reviewers to infer it.
Test scopeUse public-domain, official-sample, or owner-approved pages only when testing OCR and translation output.

If a listing cannot show package ownership, signing evidence, source links, support, pricing, and the no-chapter-hosting boundary together, treat it as a discovery mention and send installation traffic back to the official Nayovi download page.

Reviewers can request a redeem code and sample-safe test context through support before publishing a hands-on Android OCR translation review.

Owner confirmation

Which APK trust fields are confirmed

Use this before publishing a directory listing, app review, newsletter item, or partner packet so pending verification details are not guessed.

Confirmed nowOfficial domains, download URL, current APK file metadata, pricing, support, privacy, terms, and responsible-use links.
Owner must confirmPackage name, signing-certificate fingerprint, Android developer verification status, official screenshots, and any public tester report rights.
Do not inferDo not copy package or verification claims from mirrors, screenshots, third-party APK pages, or community comments.
2026 rolloutFor Android developer verification coverage, cite pending package, signing, and registration fields as owner-confirmation required until the official owner supplies exact public facts.

A repo-native trust profile is available for reviewers who need a neutral packet instead of a product page: docs/seo-distribution/android-apk-trust-profile.md.

Keep any missing package, signing, or verification fields marked as owner-confirmation required until Nayovi confirms the exact values.

Android 2026

Developer verification readiness

Use this language for reviewers, directories, and Android newsletters that ask how Nayovi handles the 2026 Android developer verification rollout.

Reviewer wordingNayovi is an official direct APK workflow; package name, signing fingerprint, developer verification status, and package registration state are pending owner confirmation.
Owner evidenceThe owner must confirm package identity, signing-certificate fingerprint, Android Developer Console or Play Console registration state, and any public verification language.
Allowed citationCite the official download page, current APK metadata, support, pricing, privacy, terms, and responsible-use guide while those release identity fields remain pending.
Blocked citationDo not state or imply Google Play approval, Android developer verification, store availability, or third-party endorsement before those facts are confirmed.

The correct public stance is pending-language readiness: Nayovi can provide official source links and current APK metadata now, while package registration, signing fingerprint, and Android developer verification fields must wait for owner-confirmed release identity facts.

This protects reviewers from copying unsupported mirror claims and gives directory editors a clear reason to preserve the official download page as the source of truth.

Citation readiness

Before a third party mentions Nayovi

Use this packet before sending Nayovi to manga media, Android newsletters, AI directories, app reviewers, localization teams, or creator-platform contacts.

Media or podcast noteLead with the OCR QA checklist, approved-sample boundary, and human-review notes before mentioning install links or review codes.
Directory noteConfirm the listing can show trial plus paid-token pricing, source-of-truth links, support, privacy, terms, and no-chapter-hosting language.
Localization partner noteUse a no-link resource note first and ask whether approved-sample OCR observations are useful; do not imply catalog access or replacement of professional localization.
Android policy noteKeep package name, signing fingerprint, and developer verification status marked owner-confirmation required until the exact public facts are confirmed.

A useful third-party mention should help readers verify the official APK source, understand the hosted OCR workflow, and know which samples are safe to process before it sends anyone to a download button.

If the platform is mainly a podcast, newsletter, creator community, or localization studio, use the comic OCR checklist or approved-sample pilot guide as the first reference and keep the product link optional.

Submissions

Before submitting Nayovi to newsletters or platforms

Use this gate before suggesting Nayovi to Android newsletters, creator-platform contacts, AI directories, or launch communities.

Android newsletterSubmit only a developer-facing checklist about independent APK trust, hosted OCR testing, and reviewer-safe screenshots; keep consumer install copy secondary.
Creator platformUse approved-sample language only and do not imply that platform, publisher, or creator catalog pages may be processed without explicit permission.
AI directoryUse accurate trial plus paid-token wording and reject listings that hide pricing, source links, support, privacy, terms, or responsible-use context.
When to waitHold any submission that needs package name, signing fingerprint, verification status, screenshots, account login, form acceptance, or public metrics until the owner confirms them.

A strong submission should be useful even if the editor removes the product link. Lead with the checklist, the APK source packet, or the approved-sample pilot scope before asking anyone to review the Android app.

Do not use a submit form, creator portal, or newsletter tip line if it requires account creation, terms acceptance, private credentials, uploaded identity documents, or unsupported claims about Nayovi package verification.

Testing

Safe Android app test packet

Use this packet when a reviewer, beta-testing service, directory editor, or partner needs a repeatable test plan before recommending the APK.

Install confidenceRecord Android version, device model, browser or file manager used, install prompt behavior, and whether the SHA-256 hash matched.
Activation pathTest free trial or redeem-code activation, token-balance visibility, device binding, and the support path for recovery questions.
OCR workflowUse only public-domain, official-sample, or owner-approved pages and note OCR progress, block order, missing text, and translation latency.
Review boundaryKeep screenshots free of copyrighted chapter pages unless the sample owner approved publication, and state that Nayovi does not host chapters.

Do not upload the APK to an external testing platform or send a redeem code until the owner approves the exact tester scope, sample pages, and publication rights for screenshots or videos.

A useful test report should cover install trust, activation, hosted OCR progress, translation review, support clarity, and the no-chapter-hosting boundary rather than only confirming that the APK opens.

Evidence

Screenshot and reviewer proof packet

Use this when an Android reviewer, app-testing service, directory editor, newsletter, or partner asks for proof they can cite publicly.

Screenshot rightsPublish only install, activation, support, or approved-sample workflow screenshots; do not show copyrighted chapter pages unless the owner approved public use.
Device matrixRecord at least one phone model, Android version, install source, network condition, and whether the reviewer tested free trial or redeem-code access.
OCR proofKeep before/after notes for detected text, missed regions, merged bubbles, reading order, correction notes, and final translation status.
Source packetAttach the official download URL, APK hash, support URL, pricing URL, responsible-use guide, and sample permission note with every review or directory listing.

A strong Nayovi review packet should make the install path, activation path, OCR behavior, sample permission, and support route visible without depending on unsupported APK mirrors or unauthorized manga, manhwa, or manhua pages.

If a reviewer wants a public screenshot set, use neutral Android workflow screens or owner-approved sample pages first, then keep any chapter-specific evidence private unless publication rights are explicit.

Handoff

How third parties should cite Nayovi

Use this handoff before adding Nayovi to an app directory, writing a review, preparing a newsletter mention, or asking for a creator-platform pilot.

Directory listing
Use the official download URL, current hash, pricing link, support link, and responsible-use guide. Do not republish the APK as an unsupported mirror-first download.
Editorial review
Request a redeem code, approved-sample screenshots, device notes, and package/signing metadata before publishing a hands-on app review.
Partner pilot
Keep the pilot limited to creator-approved, official-sample, public-domain, or owner-provided pages and confirm whether any result can be cited publicly.

The safest public citation is the official download page plus the comic OCR checklist. That gives readers the install source, metadata, support route, pricing context, and sample-permission boundary in one place.

If a third-party listing cannot show those details clearly, cite Nayovi as an Android hosted OCR workflow and send install traffic back here instead of publishing a separate APK copy.

Updates

APK source setup note

Use this note when an Android power user, APK tracker, directory editor, or reviewer wants to follow the official Nayovi APK source without relying on unsupported mirrors.

Source URLUse the official download page as the human-readable source, then use the current APK button endpoint only as the file URL.
Update checkCompare the published build label, file name, size, and SHA-256 hash before accepting an update from any tracker or directory.
Mirror boundaryDo not treat third-party APK pages as the canonical source; they should point readers back to tachiyomiat.com for support, pricing, and policy links.
Power-user noteIf using an APK source tracker, keep this page attached as the source-of-truth note so future reviews can verify the same release metadata.

A correct source setup should store the official Nayovi download page, the current APK endpoint, the SHA-256 hash, and the support URL together. That keeps update-minded Android users on the same source-of-truth path as reviewers and directories.

Nayovi does not currently claim inclusion in any third-party APK repository or automatic update catalog. Treat external tracker setup as a personal convenience until a listing is reviewed and approved through an official path.

Copyable source recipe for review packets
Keep these fields together when using a personal APK tracker, preparing a directory packet, or asking an editor to verify the official build.
Download pagehttps://tachiyomiat.com/download
APK endpoint/api/download/apk
SHA-2563ca6d69973da325f8ec03ef1c71d7cd8f4b63b8958498ef7bb8633cc9dc62bef
Supporthttps://tachiyomiat.com/support

Package-name, signing-certificate, and Android developer verification details should be added only when they are confirmed in the release packet. Until then, mark those fields as pending instead of guessing.

More help

Need setup or support?

Use these links if you want to understand the hosted flow before installing.