How to Convert InPage (.INP & .QPS) Files to Word & PDF Without InPage

1. The 30-Year InPage Dilemma: Why Modern Computers Cannot Open .INP Files

First released in 1994, InPage Urdu revolutionized South Asian printing and publishing. Before InPage, Urdu newspapers, books, and judicial documents were drafted by calligraphers (katibs) by hand on photolithographic plates. InPage introduced digital typesetting based on the traditional Nastaliq script—a complex, cursive calligraphic style characterized by descending vertical baselines, thousands of context-sensitive character ligatures, and slanted letter combinations.

However, InPage was engineered in an era preceding modern international Unicode standardization. To achieve rapid typesetting on hardware of the 1990s (like 486 and Pentium PCs running Windows 95), InPage designed a closed, proprietary 16-bit binary encoding structure. Instead of storing standard character codes, InPage stored font-specific glyph indices tied directly to its proprietary Noori Nastaliq vector font engine.

When you attempt to open an .inp file on macOS, Windows 11, iOS, or Android using Microsoft Word or Adobe Acrobat, the application fails or displays unreadable strings of random symbols (such as ÃØÝ ÝÞØ ÞÇáÈ). Without an active InPage installation—which historically required hardware parallel/USB security dongles—millions of historical archives, literary manuscripts, court petitions, and textbooks remained locked inside an obsolete format.

2. The Architecture of .INP and .QPS: Document vs. Publication Layout Files

Users working with InPage files typically encounter two distinct file extensions:

3. How Client-Side Unicode Transcoding Works

Modern conversion tools like SwiftUtils bypass the need for native InPage desktop software by operating directly on the raw binary file stream inside the web browser. The extraction process follows four essential stages:

1. Binary Stream Decapsulation: The file is read via HTML5 FileReader into an ArrayBuffer. The parser verifies magic bytes, extracts record table offsets, and skips proprietary style/ruler headers.
2. Glyph Transcoding to Unicode: Every 16-bit word is evaluated against an authoritative mapping table that correlates InPage font glyph indices to universal UTF-8 Unicode characters (U+0600–U+06FF). This properly reconstructs isolated, initial, medial, and final forms of Urdu letters (e.g., Bari Ye ے, Chhoti Ye ی, Do-Chashmi He ھ, and Gol He ہ).
3. Bi-Directional Normalization: Urdu is written right-to-left (RTL). When an InPage document contains embedded English words (e.g., proper nouns, dates, website URLs) or numbers, the text runs are normalized so that punctuation (such as the Urdu full-stop ۔ and commas ،) attaches to the correct sentence boundary.
4. OpenXML DOCX & Vector PDF Packaging: The normalized text is wrapped into a modern OpenXML ZIP archive (.docx) using client-side JavaScript. Paragraphs are configured with native RTL flags (<w:bidi/>) and right justification (<w:jc w:val="right"/>). For PDF export, the document is formatted with A4 page rules and embedded OpenType Nastaliq web fonts.

4. Recommended Typography Settings in Microsoft Word

Once you download your converted .docx file from SwiftUtils, you can open and edit it directly in Microsoft Word, Google Docs, Apple Pages, or LibreOffice. For the most authentic typographic appearance matching classical InPage printing, follow these recommendations:

5. Practical Troubleshooting Checklist

• Corrupted Header Alert: If the converter reports "Failed to parse InPage file format", verify that the file has not been truncated by an incomplete email transfer or damaged floppy/CD drive. Ensure the file extension is genuine .inp or .qps.
• Punctuation on the Wrong Side: If periods or question marks appear on the right side of a line instead of the left, confirm that your text editing software has paragraph direction set to Right-to-Left (RTL) rather than standard Left-to-Right with right alignment.
• Searchability in Search Engines & AI Models: Because the output from SwiftUtils is 100% standard Unicode UTF-8, you can paste the resulting text directly into search engines, Google Translate, ChatGPT, Claude, or relational databases for full-text indexing and semantic search.

6. Verified Capabilities & Honest Limitations

SwiftUtils is designed as a high-fidelity text extraction and document modernization engine. For complete transparency:

• 100% Supported: Full Urdu, Arabic, and Persian text runs, Nastaliq ligatures, titles, body copy, and bilingual English inserts.
• Sequential Layout Extraction: In multi-column newspaper layouts (.qps), text across independent columns is extracted in reading order rather than maintaining absolute desktop publishing coordinate boxes.
• Graphic Shapes Excluded: Proprietary InPage vector shapes, custom borders, and bezier ornament paths are omitted during text-focused conversion.
• Strict Client-Side Privacy: Zero bytes of document data or text content ever leave your browser. All decoding runs entirely in memory.