Initializing... drag & drop files here
Supports: ODT
Turn each page of an OpenDocument Text file into a JPEG you can attach, upload, embed or post anywhere — no LibreOffice, no viewer, no plugin at the other end. The page is laid out exactly as it would print and then rendered to pixels at a resolution you choose, so tables, headers, footers and font styling survive intact even though the text stops being text. The output extension on this page is fixed at .jpg; if a system demands the four-letter spelling, use ODT to JPEG instead — same conversion, different filename.
| Quality Preset | JPEG quality value | What it looks like on a text page |
|---|---|---|
| Highest | 100 | Effectively artefact-free; the largest file by a wide margin |
| Very High (default) | 95 | No visible fringing around type at normal zoom |
| High | 90 | Clean; the usual sweet spot for sharing |
| Medium | 80 | Faint ringing appears around dark text on white |
| Low | 70 | Visible haloing on small type; fine for thumbnails |
| Very Low | 60 | Blocky edges; readable but obviously compressed |
| Lowest | 50 | Heavy artefacting; only for previews |
Resolution and quality are separate levers and they fail in different ways. Too low a Conversion Quality produces detail that was never rendered — the letterforms themselves are coarse. Too low a Quality Preset produces detail that was rendered and then thrown away — the letterforms are fine but ringed with compression noise. If your output looks wrong, work out which of the two you are seeing before changing anything.
| JPG | PNG | |
|---|---|---|
| Compression | Lossy — always, at every preset | Lossless at the Highest preset; palette-optimised otherwise |
| Behaviour around sharp text edges | Ringing and haloing, worst on dark text over white | Clean edges at any zoom |
| Transparency | None — the page is flattened onto a solid colour | Alpha channel supported |
| Typical size, text-heavy A4 page at 300 DPI | Smaller, often by several times | Larger |
| Typical size, page dominated by photographs | Much smaller | Larger still |
| Universal acceptance by upload forms | Yes, the safest possible answer | Almost as broad |
| Choose it when | Size or compatibility is the binding constraint | Text legibility or transparency matters most |
If the page is mostly type, ODT to PNG will usually look better. If the page is mostly imagery, or if something at the other end will only take a JPEG, stay here.
JPEG has no alpha channel, so a transparent page background cannot survive the conversion — it has to become some solid colour. Two things make sure that colour is white rather than black: the Image Transparency control on this page opens on White, and the JPEG encoder itself is pinned to a white matte so nothing ever comes out with a black page. You can pick any of the other twenty-four colours in the Image Transparency list if you want a coloured page instead, but "no background at all" is not an option JPEG can express. That requires PNG.
Several — one JPG per page, numbered in page order, downloadable individually or as a single archive. JPEG files hold exactly one image, so there is no way to stack pages inside one. If you want every page kept together in a single file, that file needs to be a PDF: convert your ODT to PDF instead.
150 DPI is comfortable for reading on a screen and keeps files modest. 300 DPI is the default here and the right choice for printing or for pages that will be zoomed into. Go to 400-600 DPI only when the type is very small or when the image will be fed to OCR, which generally wants around 300 DPI of glyph detail as a floor. Remember that pixel count scales with the square of DPI — moving from 150 to 600 DPI makes each page sixteen times larger, not four.
That is JPEG's block-based transform reacting to hard black-on-white edges, and it is the format's oldest and most recognisable weakness. Raising the Quality Preset to High or Very High reduces it; raising the render resolution reduces it further, because each letter edge is then spread across more pixels and the transform has less of a discontinuity to encode. If you need it gone entirely rather than reduced, the answer is a lossless format — ODT to PNG or ODT to TIFF.
Yes. In Image Compression, switch from Quality Preset to "Specific file size" and enter your target in bytes, kilobytes or megabytes. Leave Auto Scale enabled and the converter is allowed to reduce the pixel dimensions when quality reduction alone cannot reach the target — which matters on text pages, because there is a floor below which JPEG simply cannot shrink a detailed page further without becoming unreadable.
Not by conversion. Rasterising discards the characters, fonts and structure and keeps only coloured pixels, so nothing in the file knows what the words were. OCR software can read them back with reasonable accuracy from a 300 DPI render, but it will make mistakes, and it will not recover the original styles, tables or layout. Keep the ODT, or produce a PDF, whenever the text has to remain machine-readable.
No. The author name, revision history, comments, tracked changes and document properties stored inside the ODT's XML parts do not exist in JPEG's model of the world; only the visible rendered page comes across. That is genuinely useful when you are sharing a page and would rather not ship the document's editing history with it — but do not rely on it as a redaction tool, since anything actually visible on the page is still visible in the image.
There is no sign-up and no watermark. Your file travels over an encrypted TLS connection, is processed on our servers, and is deleted automatically a few hours after conversion — never shared or made public. The practical constraint is upload size and connection speed rather than a fixed page cap. If the finished JPGs are what is too big, run them through the image compressor or drop the Conversion Quality a step before converting again.