Q.Can scanned PDFs be translated?
Yes. Image-only pages are detected and processed using text recognition, including mixed documents where only some pages are scanned. Results depend on the quality, resolution, and readability of the scan. When the original Word or Hancom document is available, uploading the source file will usually provide more accurate text extraction and formatting.
Q.Will the layout change if translated text is longer?
Translated text may take up more or less space than the original. qlot adjusts spacing, line breaks, and text placement to retain the document structure as closely as possible. Documents with highly complex layouts may still benefit from a final review.
Q.Can I edit the translated PDF afterwards?
You can edit the downloaded file using compatible PDF editing software. For documents that require extensive revisions, translating the original Word, PowerPoint, or Hancom file is recommended.
Q.Do I need to install anything?
No. PDF translation runs in your browser, so no additional software or plugins are required.
Q.Are .doc files supported?
qlot accepts Word documents in the .docx format. To translate an older .doc file, open it in Microsoft Word and select Save As > Word Document (.docx) before uploading.
Q.Is the table of contents translated automatically?
Yes. Table-of-contents entries are translated while the underlying reference structure is retained. After downloading the translated document, update the table of contents in Word to refresh page numbers and other field values.
Q.What happens to documents with tracked changes?
Tracked revisions and comments are translated together with the document. When only the final approved text should be translated, accept all changes and remove unnecessary comments before uploading.
Q.Can I continue editing the translated document?
Yes. The translated file is returned in the .docx format and can be opened, reviewed, and edited in Microsoft Word or compatible document software.
Q.Will translation change my formulas?
No. Formula cells are excluded from translation. Functions, expressions, and cell references remain connected to the original workbook data.
Q.Which cells are translated?
qlot translates text stored in standard text cells. Formula cells, numeric values, and date values are not translated. Text used in supported chart titles, axis labels, legends, and sheet names may also be translated.
Q.Does qlot handle workbooks with multiple sheets?
Yes. All worksheets are processed together, with their order and individual structure retained. Terminology can be translated consistently across related sheets within the same workbook.
Q.Are numbers, dates, and currencies changed?
No. Numeric and date values remain unchanged. Existing display formats, including currency symbols, percentages, decimal formats, and date patterns, remain applied to their cells.
Q.Are charts and formatting retained?
Chart structure, data series, cell formatting, merged ranges, borders, fills, and conditional-formatting rules remain in place. Supported chart titles, labels, and legends are translated with the workbook text.
Q.Will translated text overflow its text boxes?
Translated text may take up more or less space than the original. qlot adjusts font size and line spacing within the available text area to reduce overflow and retain the slide structure. Presentations with dense text or large differences in language length may still benefit from a final visual review.
Q.Are speaker notes translated?
Yes. Speaker notes are translated together with the content of their corresponding slides.
Q.Are tables and charts translated?
Supported text within tables is translated while the existing cell structure remains in place. Chart titles, axis labels, and legends are also translated while the underlying chart structure and data remain unchanged.
Q.Are animations and transitions preserved?
Existing object animations and slide transitions remain attached to the presentation. They are retained rather than rebuilt during translation.
Q.Why do I need to convert .hwp files to HWPX?
qlot processes Hancom documents in the HWPX format. HWPX uses a structured document format that allows supported text, layouts, tables, and other document elements to be processed. To convert, open the .hwp document in Hancom Office, choose Save As from the File menu, and select HWPX Document as the file type, then save the converted file. Review the converted document before uploading, particularly when it contains complex formatting, WordArt, or other Hancom-specific objects.
Q.Will official document forms and tables remain intact?
qlot retains supported page layouts, table structures, merged cells, frames, page numbers, headers, and footers. When translated text requires more space, content is adjusted within the available layout. Documents with dense tables or complex proprietary objects may benefit from a final review.
Q.What happens to Hancom-specific objects?
Standard document text, tables, frames, footnotes, headers, and footers are processed with the document. Some proprietary objects, including certain WordArt elements, may be retained as images rather than translated as editable text.
Q.Can I edit the translated document afterwards?
Yes. The translation is returned as an HWPX file that can be opened and edited using compatible Hancom software.
Q.Will a transparent logo still be transparent after translation?
Yes, when the PNG is transparent through an alpha channel or a palette entry: the delivered PNG is transparent too, so the translated wordmark can be placed over any background at the same pixel size.
Q.How are buttons, menus, and dialog text handled in screenshots?
AI vision reads the interface text and translates it with the whole screen as context, so the wording suits the role of each control rather than being handled line by line, then sets it back in the same position. Since the screenshot is regenerated rather than patched pixel by pixel, fine detail such as a drop shadow may be re-rendered, but toolbars, icons, and flat colour areas come back recognisably the same.
Q.What happens to a 16-bit or palette PNG?
Both are accepted. Output is 8-bit per channel, so a 16-bit PNG or an indexed-colour PNG is returned as a standard 8-bit PNG at the original width and height: truecolour for colour sources, greyscale for greyscale sources. The embedded colour profile is kept, and transparency is kept when it comes from an alpha channel or a palette entry, so a cut-out logo saved as an indexed PNG still comes back transparent.
Q.Which PNG uploads are declined or fail?
Animated PNG (APNG) and images whose shorter side is under 256 pixels are declined before any charge. Images without readable text, and extremely tall or wide captures of around 3:1 or more like a full-page scroll or banner, are not processed and nothing is charged. One still image is processed per upload, so split a scrolling-page capture into screen-height pieces and upload each one.
Q.Does the translated JPG still record where the photo was taken?
No. The delivered JPG carries no device name, capture date, or GPS coordinates, so a phone photo of a menu or shopfront no longer records where it was taken. Only the EXIF block goes. The photo's ICC colour profile stays embedded, so the file is read in the same colour space as the upload and still opens as an ordinary JPG. Keep your original if you need the shooting data later.
Q.Does the translated JPG keep the original compression quality?
Yes. The delivered file is encoded with your upload's own quantisation tables and chroma subsampling, whether 4:4:4, 4:2:2, or 4:2:0, rather than a generic quality setting. A progressive JPEG comes back progressive, and the width and height are unchanged, so the file drops into a website or catalogue in place of the original.
Q.Can I translate a scanned page saved as a JPG?
Yes. A scanned letter, form, or book page is read by AI vision like any other photograph, and the translated text is set back on the page in its original positions. The result is still a picture of the page. If you have the original document file the scan came from, translating that instead gives you editable text.
Q.Which JPG uploads are declined?
Images whose shorter side is under 256 pixels are declined before anything is charged. Both .jpg and .jpeg extensions are accepted, one image per upload. A photo with no readable text, or one whose long side is around three times its short side or more, is not processed and not charged.
Q.Do I get a HEIC back, or a JPG?
A HEIC. The translated photo is written in the same format your device saved, at the same pixel dimensions and with the same colour profile, rather than converted to JPG along the way. Translation never changes the file type. If you do want a JPG or PNG, qlot's separate image conversion feature handles that afterwards.
Q.Does a 10-bit HEIC keep its colour depth?
No. Delivery is 8 bits per channel, so a 10-bit HEIC from a recent iPhone comes back as a standard 8-bit HEIC with the Display P3 profile carried over, at the same pixel dimensions.
Q.Do the camera details and GPS stay in the translated HEIC?
They are removed. EXIF and camera metadata, including the device model, capture date, and GPS coordinates, are not written into the delivered HEIC, so sharing the translation does not share where you took it. If you need the capture date or location later, keep the original in your photo library, because the translated HEIC carries neither.
Q.Which HEIC files are declined?
Bursts and other multi-image HEIF sequences are declined, since only a single still is translated, as are photos with no readable text and photos whose shorter side is under 256 pixels; none of these is charged. An extremely wide or tall shot, around 3:1 or more, such as a full-length receipt or a banner, may not be processed, and an upload that fails with an error is never charged either.
Q.What is the difference between HEIF and HEIC?
.heif and .heic are two extensions of the same HEIF container, so the same width, height, colour profile, and transparency rules apply to both. qlot accepts both and returns each with the extension it arrived with, so a .heif stays .heif and a .heic stays .heic.
Q.Is a 10-bit HEIF from my camera supported?
Yes. The text is read and translated from the full image, and the result is written back as a standard 8-bit HEIF. If you need the original bit depth for grading or printing, keep the original capture alongside the translated copy, since the delivered file is 8-bit per channel.
Q.Will the colours in my HEIF shift after translation?
Colours are approximated from the source when the image is regenerated; the embedded ICC profile is carried over so the result is interpreted in the same colour space, and an RGB HEIF stays RGB while a greyscale one stays greyscale. Bit depth is the one thing that does change: a 10-bit capture comes back as standard 8-bit colour.
Q.Which HEIF files are declined before translation?
HEIF bursts and image sequences, which hold several frames in one container, are declined before any charge, as are images whose shorter side is under 256 pixels. Save the single frame you want and upload that. A HEIF with no readable text, or an extremely wide or tall one, around 3:1 or more, such as a long receipt or a banner, is not processed; the upload fails with an error and nothing is charged.
Q.Will a lossless WebP come back lossless?
Yes. The encoding of the upload is kept: lossless in, lossless out, and lossy in, lossy out, at the pixel dimensions of the original. The file is never converted to PNG or JPG, and any EXIF block the export carried is dropped. Because the image is regenerated rather than pixel-edited, fine texture may be re-rendered; the picture remains recognisably the same.
Q.Is the transparent background kept on a cut-out product image?
Yes. When the WebP has an alpha channel, the delivered image has the same transparency, so a product cut-out still sits on whatever background the page gives it. For a lossless WebP the delivery is lossless and the encoder keeps the colour values of fully transparent pixels rather than discarding them.
Q.Can I translate an animated WebP or a wide banner?
No for animations: a multi-frame WebP is declined before any charge, since the translation works on a single still frame. Save the frame with the text as its own WebP and upload it. Very wide or tall strips, at around 3:1 or beyond, may not be processed; the task then fails and nothing is charged. A thumbnail whose shorter side is under 256 pixels is declined before any charge.
Q.Can I edit the translated text in the WebP?
No. The download is a WebP image, so the translated headline and button copy are pixels rather than editable text layers. To keep the text editable, translate the design file the banner was exported from and re-export it. To publish the banner as a PNG or JPG rather than a WebP, use qlot's separate image conversion feature.
Q.Will the translated file still open in my spreadsheet or import tool?
Yes. The delivered CSV keeps the delimiter, quoting, line endings, and encoding of the upload, and every non-text cell is copied through unchanged, so column positions and data types are exactly as exported. If the target language cannot be written in the original encoding, the file is delivered as UTF-8 with a byte-order mark, which Excel and most import tools read correctly.
Q.Does qlot change numbers, dates, or product codes?
No. A cell that holds a number, date, boolean, URL, email, identifier, or formula is recognised as data and reproduced verbatim, leading zeros included. Only cells that contain text in the source language are translated.
Q.Is the header row translated?
Yes. Column headings are translated with the same per-cell rules as the rest of the file, so a heading that is a code stays a code while a descriptive heading is translated.
Q.Which CSV files are declined?
Files whose encoding cannot be detected, whose delimiter cannot be determined, or that contain no text in the source language are declined before any charge, as are files with millions of cells. If the translation comes back largely unchanged, the task fails and nothing is charged. Each upload is a single CSV file.