How it works
EditPLR takes a finished document apart, hands you every piece as something you can edit, and writes your changes back into the file you started with. Here is each step, and what it can and cannot do today.
1. Opening the file
You point the editor at the PDF that came with your pack. It is read where it sits; there is no upload step.
A PDF stores text as individual characters placed at coordinates on a page. EditPLR reads those positions and works out which characters form a line, which lines form a paragraph, and which paragraph is a heading rather than body text. It uses the geometry — left edges, line spacing, font size — rather than guessing from the words.
Pictures are pulled out as real image files, with their pixels intact. Page furniture that repeats in the same spot on every page, such as a running header, is marked as such so it does not end up as a chapter of your new book.
What will not open
- Scanned PDFs. A scan is a photograph of a page. There is no text inside it to recover, and EditPLR does not read text out of images.
- Word files (.docx). Not supported. The editor opens PDFs. A Word path exists in the reference engine that was never carried into the browser version, so there is nothing here that would read your .docx.
- Password-protected files. Remove the protection first, if your licence allows it.
2. Editing
Every heading, paragraph and image becomes a block you can act on. You can rewrite the text, delete blocks entirely, move them into a different order, and replace pictures with your own.
This is the part that matters. Re-exporting a pack in a nicer font leaves you with the same sentences that every other buyer of that pack is also publishing. The rewriting is what produces something that is actually yours — and it is work no tool can do for you honestly.
A good rule from people who do this for a living: change the title, the introduction, the conclusion, and enough of the body that the piece argues in your voice rather than a generic one.
3. Exporting
The editor builds a fresh PDF from your blocks — your cover, your author name, your layout. Nothing of the original design carries over unless you put it there.
The table of contents is generated during export rather than copied from the original, so its page numbers always match the document you actually produced.
Where the project is today
Reading PDFs in the browser is built and tested: text, paragraph grouping, page furniture, image positions and image pixels all come out correctly, measured against files where we know exactly what went in.
The editor runs as an early preview and currently opens a prepared catalog file. Connecting it to your own uploads, and moving PDF export into the browser, are the steps still in progress. The privacy page says plainly which parts have been measured and which have not.