CONVERT
LIT → RST
Tap to choose your fileDRAG. DROP. DONE.
Upload any file and our engines will handle format detection automatically.
Max 25 MB · Free plan · No signup required
Convert to:
Detecting available formats...
Optimize for
Leave empty to use original name. Extension added automatically.
Uploading...
Processing your file...
Fast, secure LIT to RST conversion. No registration required.
Setup: LIT is Microsoft Reader's legacy ebook format, discontinued since 2012. Goal: an interchangeable RST. A RST from a LIT lets you move ebook content back into a traditional document workflow — editorial review, proof-reading, print production, legal archiving. The conversion is lossless for the text and images; pagination is recreated deterministically. In practice LIT is Microsoft Reader's legacy ebook format, discontinued since 2012. On the other end, RST is a document format oriented around a particular office suite or publishing pipeline.
Microsoft LIT
Source formatLIT is a legacy Microsoft Reader eBook format, now obsolete.
reStructuredText
Target formatRST (reStructuredText) is a lightweight markup language used in Python documentation.
Why convert LIT to RST
Retailers and printers often demand RST submissions rather than LIT. Converting up front gives you control over the pagination and styling rather than leaving it to their automated ingest pipeline.
HOW TO CONVERT
LIT → RST
Provide the LIT
Drag-and-drop the ebook up to 25 MB. No account required on the free tier.
Rewrite to RST
The pipeline preserves heading structure, lists and images while adding page geometry the RST expects.
Retrieve the output
Click to download the RST. Open it in Word, LibreOffice or any document editor.
Common Use Cases
Share across platforms
Send RST files to anyone without worrying about whether they have the right software for LIT.
Embed in documents
Drop RST output into Word, Google Docs, PowerPoint, Notion or a website without conversion warnings.
Optimize size
RST often produces smaller files than LIT for web, email and storage.
Archive & future-proof
Store in a widely-supported format that will still open on future operating systems without legacy plugins.
LIT vs RST — Strengths and limitations
What each format does best, and where it falls short.
LIT Strengths
- Good rendering quality via ClearType in its era.
- Efficient compression via LZX.
- Small file sizes for text-heavy books.
Limitations
- DRM activation servers are permanently offline — DRM-protected purchases are dead weight.
- Proprietary format with no vendor successor.
- Zero modern reader support (Windows, macOS, iOS, Android).
RST Strengths
- Rich directives for admonitions, code, math, and custom elements.
- Cross-references work within and across documents.
- Sphinx ecosystem offers best-in-class Python docs output.
- Standardized as part of Python PEP infrastructure.
- Plain text, version-controllable.
Limitations
- Syntax denser than Markdown — higher learning curve.
- Less widely adopted than Markdown outside Python world.
- Multiple directive dialects (Sphinx, Docutils, custom) create fragmentation.
LIT vs RST — Technical specifications
Side-by-side comparison of the technical details.
LIT
- MIME type
- application/x-ms-reader
- Extension
- .lit
- Container
- CHM-like (LZX-compressed OEBPS)
- DRM
- Microsoft Reader activation (servers offline since 2012)
- Status
- Retired
RST
- MIME type
- text/x-rst
- Extension
- .rst
- Toolchain
- Docutils, Sphinx, Read the Docs
- Encoding
- UTF-8
- Related formats
- MyST (Markdown + RST directives)
| Specification | LIT | RST |
|---|---|---|
| MIME type | application/x-ms-reader | text/x-rst |
| Extension | .lit | .rst |
| Container | CHM-like (LZX-compressed OEBPS) | — |
| DRM | Microsoft Reader activation (servers offline since 2012) | — |
| Status | Retired | — |
| Toolchain | — | Docutils, Sphinx, Read the Docs |
| Encoding | — | UTF-8 |
| Related formats | — | MyST (Markdown + RST directives) |
LIT vs RST — Typical file sizes
Approximate file sizes for common scenarios.
LIT
- Novel (text only) 200 KB - 1 MB
- Illustrated book 2-10 MB
RST
- API reference page 5-50 KB
- Sphinx project chapter 20-100 KB
- Full library documentation 500 KB - 10 MB
Quality & Compatibility
Images re-embed at their original resolution; vector figures convert to PNG where the RST does not support vector primitives. Tables maintain row/column structure but simple layouts travel better than complex nested grids.
Tips for Best Results
- Set page size (A4 vs Letter vs 6x9 trim) explicitly in Advanced when producing a print-ready RST — the default is A4.
- If chapter breaks disappear in the RST, enable "force section break before H1" in Advanced to insert a hard page boundary at every chapter.
- Keep the LIT original; future-proofing your manuscript means always being able to regenerate downstream formats.
Frequently Asked Questions
Yes. The free tier accepts files up to 25 MB without registration, email capture or watermarks; paid plans go up to 2 GB. Paid plans raise the size cap, enable batch conversions and provide a REST API for automation, but nothing on the free tier is quality-limited — the output is exactly the same as on any paid plan.
Yes when the source LIT tags chapter starts semantically (H1 / section boundaries). Each chapter becomes a new section in the RST with a page break before it. If the LIT uses only visual cues like larger font sizes, enable "detect chapters heuristically" in Advanced so we still produce clean breaks.
Uploads run over HTTPS, files are processed in isolated containers, and both the source LIT and the RST output are auto-deleted within two hours. No account is required, file contents are never logged, and KaijuConverter does not use uploads for AI training. The paid plan adds a signable data-processing agreement for regulated workflows.
Yes. The cover from the LIT becomes the first page of the RST (or is moved to metadata depending on document conventions). Inline images re-embed at their source resolution; you can toggle "optimise images" in Advanced to shrink the RST file size.
Most files finish in well under a minute. Small images and documents are typically ready in a few seconds; large video or audio files scale roughly with duration. Upload speed from your network is usually the dominant factor, not server time.
Yes. We produce a clean RST with paragraph and heading styles mapped to standard document styles. Open it in Word, LibreOffice or Google Docs and you can edit, comment and track changes just like any native document.
Related comparisons
See these formats side by side to understand which fits your use case best.
Related Guides
PSD Adobe Photoshop Format: Understanding the Industry Standard
Complete guide to PSD Photoshop format: 5-section file structure, layer types (pixel/adjustment/text/smart object), blend modes, masks, PSB large documents, and export commands.
Read guideSQLite Format: Complete Guide to the World's Most Deployed Database
Complete guide to SQLite database format: page structure, B-tree organization, record encoding, WAL journaling mode, when to use SQLite vs PostgreSQL, and SQLite inspection tools.
Read guideRTF Format: Rich Text Format Document Guide — Structure, Compatibility & Conversion
Learn what RTF files are, how Rich Text Format stores formatted text, why it remains a universal document standard, and how to convert RTF to DOCX, PDF, or ODT.
Read guideSecure & Private Conversion
Your files are encrypted during transfer, processed in isolated containers, and automatically deleted within 60 minutes. We never read, share, or store your data.