Format-specific parameters

Tenant-level settings for fine-tuning how the parser handles HTML, PDF, and Word documents at the format level.

Renamed HTML Tags

Type	Text field
Default	Empty

Accepts semicolon-separated instructions that remap HTML tags to different element types or exclude elements by CSS class from parsed output. Enter instructions in one of two forms:

Tag renaming: tag=X,replacetag=Y Instructs the parser to treat tag X as if it were tag Y. For example, tag=span,replacetag=h2 causes the parser to interpret every <span> element as a heading.

Class exclusion: a plain CSS class name Causes the parser to exclude every HTML element whose class attribute exactly matches the entry from parsing entirely, including all its children.

Both forms can be combined in a single value:

tag=span,replacetag=p;tag=button,replacetag=h3;navpage-header;page-footer

All matching is case-insensitive.

HTML Parameters

Type	Text field (JSON)
Default	Empty

Accepts a JSON object that fine-tunes HTML document parsing behavior. Configure one or more of the following keys:

Key	Type	Default	Description
excludedHeaders	Array	-	Header tags to exclude from heading detection when parsing PDFs and Office documents converted to HTML. Has no effect on native HTML documents. Example: ["h4","h5","h6"]
excludedPages	Array	-	1-based page numbers to skip entirely during parsing. Example: [1,3]
headerFrequency	Integer	10	Minimum number of times a heading subject must appear in PDF-converted HTML before the parser promotes it as a section header. Minimum value: 1
faqDeduplication	Boolean	-	When true, screens early sections before applying FAQ detection. If a section fails the FAQ content check, it is preserved as regular content and screening ends, preventing content such as a table of contents from being misclassified as FAQ material.
version	Integer	-	Set to 3 or higher to enable experimental HTML flattening that pre-processes document structure before section detection

Example:

{"excludedHeaders": ["h4","h5","h6"], "headerFrequency": 5, "faqDeduplication": true}

Use excludedHeaders or excludedPages when minor heading levels or specific pages such as cover or index pages create unwanted section splits. Use headerFrequency when PDFs converted to HTML produce noisy section detection due to frequently repeated minor headings.

Invalid or blank JSON falls back to defaults for all sub-parameters.

PDF Parameters

Type	Text field (JSON)
Default	Empty

Accepts a JSON object that customizes PDF parsing behavior. Several keys require enhancedPhotoMode: true to take effect.

Top-level keys:

Key	Type	Default	Description
imageResolution	Integer	144	Resolution in dots per inch at which the parser renders PDF pages as images. Range: 72–360. Higher values produce sharper images at the cost of larger file sizes.
enhancedPhotoMode	Boolean	-	When true, uses font analysis to identify document sections. Also acts as a fallback parsing mode when the PDF converter is unavailable.
subjects	Array	-	Replaces the default subject keywords used to identify section headings (chapter, section, article, part, paragraph, articolo). Requires enhancedPhotoMode: true.
annexes	Array	-	Replaces the default appendix keywords used to detect appendix sections (appendix, annex, annexe, appex, załącznik, attachment, allegato). Requires enhancedPhotoMode: true.
pdfConfiguration	Object	-	Nest object for advanced document segmentation. Accepts links, pdfSegments, and strategy keys. Requires enhancedPhotoMode: true for pdfSegments and strategy.

The pdfConfiguration key accepts a nested object with the following keys:

Key	Description
links	Represents a PDF as a single linked section instead of parsed text. Each entry requires a pdfName value: a filename or "all", and optionally title, linkText, and text.
pdfSegments	Manual section definitions for specific PDFs. Each entry requires a pdfName (exact filename) and a sections array. Each section has subject, sentence, and pageNo (1-based, as a string). If pdfSegments is non-empty, strategy is ignored. Requires enhancedPhotoMode: true.
strategy	Page range strategies for specific PDFs. Each entry requires a pdfName (supports "all") and a strategies array. Each strategy has strategyName ("PRESENTATION" or "BOLD_FONTS"), startPage, and endPage (both strings). Ignored if pdfSegments is non-empty. Requires enhancedPhotoMode: true.

Example:

{
  "imageResolution": 200,
  "enhancedPhotoMode": true,
  "pdfConfiguration": {
    "pdfSegments": [
      {
        "pdfName": "policy-document",
        "sections": [
          {"subject": "Introduction", "sentence": "This policy applies", "pageNo": "1"},
          {"subject": "Scope", "sentence": "The following teams", "pageNo": "2"}
        ]
      }
    ]
  }
}

Use imageResolution to adjust rendered page image quality when sections appear as images. Enable enhancedPhotoMode for PDFs with consistent structural patterns where font-based section detection improves results. Use pdfConfiguration.links to surface a PDF as a downloadable link rather than extracted text.

See also: Show sections as images

Docx Parameters

Type	Text field
Default	Empty

Defines custom Word style-to-HTML heading mappings used when converting .docx and .doc files to HTML. Enter a semicolon-separated list of entries in the following format:

StyleName,HTMLTag:mode

• StyleName: The name of the Word paragraph style to map, such as Heading 1 or Title. Also accepts bold to map all bold-formatted paragraphs, and underline to map all underlined paragraphs.

• HTMLTag: The HTML heading tag to map the style to, such as h1 or h2.

• mode: Optional. Set to fresh to create a new HTML element for each matching paragraph. Without :fresh, consecutive paragraphs sharing the same style are appended into a single element.

Example:

Heading 1,h1:fresh;Heading 2,h2:fresh;bold,h3

When not configured, the parser maps Word's built-in "Title" style to <h1> and "Subtitle" to <h2>, both using :fresh behavior by default. If the converted HTML contains no h1–h3 heading tags, the parser automatically promotes paragraphs consisting entirely of bold text to <h1> regardless of this setting. Configure this when Word documents use custom style names the parser does not recognize as headings by default, causing documents to parse as a single unstructured block.