Choose the task you need, then open its guide and tool together. Find instructions for PDF pages, supported text edits, conversions, forms and image upload requirements, with the relevant limits and checks for the saved result.
Check the destination’s file requirements first, keep your original and compare the saved result before sharing it.
本指南提供英文版。下方為英文原文，工具連結將開啟英文版。
Images, plain text, and HTML need different conversion controls because they carry different kinds of source information.
Use JPG to PDF for image pages, TXT to PDF for a plain-text file, and HTML to PDF for safe self-contained markup. These are three separate PDFKaka tools; no single one performs all three conversions.
Use JPG to PDF for photographs, receipts, screenshots, and scanned pages. Arrange the images, then choose page size, orientation, margins, and fit. Each source image becomes a PDF page.
Use TXT to PDF when the source is a text file and readable pagination matters more than rich formatting. Set font, spacing, margins, and page options, then inspect line and page breaks.
Use HTML to PDF for supported local markup. Scripts, forms, embedded pages, remote styles, and external resources are intentionally excluded, so required content must be self-contained.
An image does not become editable text merely because it is placed in a PDF. Plain text does not carry Word-style formatting. HTML can describe structure and styling, but only within the converter's safe supported subset.
No. Use TXT to PDF for plain text and HTML to PDF for supported self-contained markup.
Use JPG to PDF or Scan to PDF for page images; run OCR later only if searchable printed text is needed.
No. Remote resources and scripts are intentionally excluded from the safe conversion workflow.
The best conversion format depends on what you plan to do next. No single output preserves every part of a PDF equally well.
Choose Word for editable document text, TXT for plain text, Markdown for a lightweight draft, PowerPoint for slides, or JPG/PNG for page images. Check each tool’s text, OCR and layout limits rather than treating file extensions as equivalent.
Use PDF to Word for an editable DOCX, PDF to Text for simple UTF-8 text, or PDF to Markdown for lightweight structured text. Complex layouts and reading order remain best-effort.
Preserve appearance is the default and creates one page image per slide. Editable native text separates supported horizontal source text into real text boxes over a graphics background. Unsupported, rotated or nested text, scans and form widgets stay in the background; review fonts and placement.
PDF to JPG renders complete pages. JPG is usually smaller for photographic content, while PNG preserves rendered pixels without lossy image compression.
For a letter that needs rewritten paragraphs, start with editable Word. For a report going into a code repository, extract Markdown and repair its structure. For a page that must be shown unchanged in a presentation, choose PowerPoint appearance mode; use its explicit native-text mode only when supported source wording needs editing.
The best conversion format depends on what you plan to do next. No single output preserves every part of a PDF equally well. Editable modes can alter layout/reading order and omit graphics; appearance mode uses non-editable page images.
Not always. Editable conversion can change layout or reading order, while appearance-focused output may use page images that are not separately editable.
One PDF up to 50 MiB and 100 pages. Editable English OCR supports at most 25 scanned pages within that document. The tool reports a limit before offering an unsupported output.
No. Each workflow reconstructs only its supported content. A PNG cannot contain editable paragraphs, and a PPTX or DOCX can still hold page images when an appearance-focused mode is used.