Back to homepage

Usage guide

How to use ScanlateAI

This page explains the normal workflow from importing a chapter source to reviewing translated output in the reader.

1. Bring pages into the system

Create a job from direct image URLs or a chapter URL pattern so you can process a whole set without manual collection.

2. Let OCR and translation run together

The system extracts text first, then produces readable translated content designed for scanlation-style review.

3. Review inside the app

Use the built-in reader and dashboard flow to inspect results quickly before release or iteration.

01

Choose the right input mode

Use direct links when you already have page assets. Use pattern crawl when a chapter follows a stable URL structure.

  • Direct links are faster for small batches or mixed sources.
  • Pattern crawl is better for serialized sites with predictable page numbering.
02

Create the extraction job

In the dashboard, fill in the source details and submit the job so the worker can start collecting and processing pages.

  • Set the page range carefully when using URL patterns.
  • Only add optional selectors when the source layout needs extra targeting.
03

Wait for OCR and translation processing

The worker fetches images, extracts visible text, and sends the content into the translation flow.

  • Status updates in the dashboard help you see what is queued, running, or completed.
  • This step is where structured extraction and AI translation combine into the final text output.
04

Open the result in the library or reader

After processing completes, use the reading interface to inspect chapters as readers will see them.

  • This is the fastest way to catch layout or wording issues before release.
  • Reader-based review is usually more reliable than checking raw structured data alone.
05

Repeat with a stable workflow

Once you know the right source format for a site, the next chapters become much faster to process.

  • Teams get the most value when they standardize how jobs are created.
  • Use pricing and credit planning to match your release volume.

Best practices

Tips for smoother results

A few habits make the workflow cleaner and reduce avoidable retries.

  • Start with a short chapter or sample range when testing a new source pattern.
  • Use direct links for inconsistent sources instead of forcing a fragile crawl template.
  • Review output in the reader, not only in raw status tables, before considering a chapter done.
  • Choose pricing packages based on expected page volume, especially if your release schedule spikes.
ScanlateAI | AI Manga OCR, Translation, and Reader