Portable Document Format (.pdf)

ISO 標準

The Portable Document Format (PDF) is a ubiquitous digital paper standard designed to present documents consistently independent of application software, hardware, and operating systems.

発明者: Dr. John Warnock & Adobe Camelot Project年: 1993MIME: application/pdf

PDF を DOCX に変換

無料のブラウザ内 PDF から DOCX へのコンバーター。お使いのデバイスでファイルを即座に変換します。

PDF から DOCX へのコンバーター →

PDFをオンラインで圧縮

ブラウザ内100%ローカル圧縮 — ファイルが外部サーバーに送信されることはありません

PDFを圧縮 →

調査とメタデータ

オペレーティングシステムやファイル解析ツールは、先頭のバイナリバイトシーケンスを検査することで PDF ファイルを識別します:

ファイルを選択またはドラッグ

ここにファイルを選択またはドロップ

100%プライベートなブラウザ内変換 - ファイルがデバイスから外部に出ることはありません

または貼り付け Ctrl+V

ネットワーク送信ゼロのプライバシー保証： 外部サーバーへのデータ送信は0バイトです。すべての処理はお使いのブラウザのサンドボックス内でローカルに実行されます。

バイトレベルのヘッダーシグネチャ (マジックバイト)

オペレーティングシステムやファイル解析ツールは、先頭のバイナリバイトシーケンスを検査することで PDF ファイルを識別します:

16進数シグネチャ (オフセット 0):

25 50 44 46

ASCII表現: %PDF

標準化: ISO 32000-1 (2008) / ISO 32000-2 (2020)

技術仕様

コンテナアーキテクチャ	Binary/ASCII hybrid object hierarchy with cross-reference table
圧縮	FlateDecode (Deflate), DCTDecode (JPEG), CCITT Fax, JBIG2, JPXDecode
バイトエンディアン	Big-Endian (network byte order) for binary object streams
色空間	sRGB, Display P3, DeviceCMYK, Grayscale, Spot Colors (Pantone)
チャンネルと構造	Multi-layer vector, typography, raster streams, and embedded metadata
最大寸法	200 x 200 inches (UserUnit allows up to 15,000,000 inches in PDF 1.6+)
透過性	Full alpha transparency, blend modes, and opacity masks
ストリーミングとプログレッシブ	Linearized PDF ('Fast Web View') allows byte-range streaming via HTTP Range requests

技術比較マトリックス: PDF 対競合製品

技術属性	PDF (現在)	DOCX	EPUB	HTML5
Visual Layout Fidelity	Pixel-perfect fixed geometric layout across all screens and printers	Flow-based; varies across Word versions and installed fonts	Reflowable reader layout; no fixed typography guarantees	Fluid CSS box model; screen-dependent rendering
Self-Containment	100% self-contained with embedded fonts, raster streams, and vector assets	Self-contained XML container (system fonts usually un-embedded)	Self-contained ZIP container (packaged XHTML/CSS assets)	Requires external HTTP resources unless packaged via MHTML
Cryptographic Signatures	Native PAdES and X.509 cryptographic digital signatures built into ISO spec	Office XML DSig digital signatures supported	Requires custom digital container signatures	Requires Web Crypto API or external TLS transport guarantees
Mobile Responsiveness	Fixed-page canvas (requires zooming and panning on small screens)	Excellent responsive text reflow	Engineered specifically for fluid mobile e-reading	Native responsive layout with CSS media queries
Standardization	Open International Standard (ISO 32000-2:2020)	ECMA-376 / ISO/IEC 29500	W3C / IDPF Open Standard	W3C Living Standard / WHATWG

一般的な破損モードと16進数リカバリガイド

⚠️ Acrobat or PDF viewer reports 'The file is damaged and could not be repaired' or opens completely blank.

根本原因: FTP or HTTP transfer in ASCII mode converted binary byte sequences (replacing 0x0A with 0x0D 0x0A), mangling the cross-reference (xref) table byte offsets.

復旧: Modern PDF repair utilities (e.g. qpdf --repair or File2File repair) rescan the file linearly, rebuild the object dictionary, and regenerate a new xref table.

⚠️ PDF viewer fails to load the document or crashes on the last page.

根本原因: Truncated download or incomplete disk write missing the '%%EOF' marker and trailer dictionary.

復旧: Inspect file tail using 'tail -c 128 document.pdf'. If missing %%EOF, verify if the root catalog object exists and append an artificial xref table pointing to the highest valid object number.

⚠️ Embedded fonts render as illegible symbols, blank blocks (.notdef), or question marks.

根本原因: Non-embedded subset fonts referencing system fonts that are missing on the viewing machine, or corrupted ToUnicode CMap tables.

復旧: Re-embed missing font subsets via Ghostscript (gs -o fixed.pdf -sDEVICE=pdfwrite -dEmbedAllFonts=true broken.pdf) or convert text elements to vector curves.

セキュリティ分析とパーサー攻撃ベクトル

PDF is one of the most complex formats in computing, featuring active scripting, embedded files, and dynamic streams. Modern browsers sandbox PDF renderers (e.g. Chrome PDFium) in isolated processes.

既知の攻撃ベクター

Embedded Acrobat JavaScript (JS API) executing arbitrary code or phishing exploits upon document open.
Launch Actions (/Launch) configured to execute external system binaries or shell scripts.
Font rendering vulnerabilities in legacy Type 1 and TrueType font parsing engines triggering buffer overflows.
Server-Side Request Forgery (SSRF) and NTLM hash credential theft via malicious URI actions (/URI) or form submissions.

防御的ベストプラクティス: Never open untrusted PDFs with Adobe Acrobat JavaScript execution enabled. For web viewing, always render via browser sandboxed WebAssembly/PDF.js engines, or convert untrusted PDFs to sanitized PDF/A-1b documents.

歴史的背景とマイルストーン

2020ISO 32000-2:2020 released, formalizing modern PDF 2.0 enhancements.

2008Adobe transfers PDF specifications to the International Organization for Standardization as ISO 32000-1.

1993PDF 1.0 launched alongside Adobe Acrobat, supporting text, links, and fonts.

1991Dr. John Warnock initiates the Camelot Project at Adobe to solve digital document portability.

主な利点とメリット

100% universal visual fidelity across all devices, operating systems, and printers.
Supports digital cryptographic signatures, redaction annotations, and DRM access permissions.
Combines vector graphics, scalable fonts, and compressed raster streams into a single self-contained container.

技術的な制限とデメリット

Fixed-layout page canvas makes automatic responsive reflowing on small smartphones challenging.
Complex internal object stream hierarchy can lead to bloated file sizes without compaction and unreferenced object elimination.
Embedded JavaScript and dynamic launch action capabilities present an expansive attack surface.

興味深い技術トリビア

The original Camelot project paper envisioned printing documents electronically from any application directly to any display.
Every PDF file ends with the exact string '%%EOF' marking the end-of-file trailer.
Federal courts and national archives globally mandate PDF/A (ISO 19005) for long-term legal preservation.

よくある技術的な質問

Why do PDF files look identical on every screen and printer?

PDF specifies absolute Cartesian coordinates (points at 1/72 of an inch) for every glyph, vector curve, and raster image on a fixed page canvas. Because fonts, vector paths, and color profiles are embedded directly in the container, rendering does not depend on local system fonts or printer drivers.

What is the difference between standard PDF and PDF/A?

PDF/A (ISO 19005) is a specialized subset designed for long-term archiving. It strictly bans features that could compromise future readability, such as JavaScript, external font linking, encryption, sound/video embedding, and device-dependent color spaces. All fonts and color profiles must be 100% embedded.

How does PDF compression work in modern documents?

PDF uses multiple discrete compression filters tailored to content types. Text, vector commands, and font metrics are compressed using FlateDecode (zlib/deflate). Photographic images use DCTDecode (JPEG) or JPXDecode (JPEG 2000), while bi-level monochrome scanned text uses JBIG2 or CCITT Fax Group 4 compression.

Why does a PDF file often stay large even after deleting pages or images?

When modifying a PDF, many editors perform an 'incremental update'—they append new object streams and a new xref table to the end of the file without deleting the old objects, allowing fast undo. To actually reduce the file size, the document must undergo an optimization pass that garbage-collects unreferenced objects.