Skip to content

Convert anything, at global scale.

300+ formats and automation APIs that feel instant.

CONVERT

From

To

IMAGEAsciiDoc XPM

Convert AsciiDoc to XPM

Convert AsciiDoc to XPM online for free with no sign up, with quality-focused workflow guidance.

Reverse conversion

Drop files or choose a source

Upload multiple files at once, mix formats, and fine-tune every conversion with format-aware settings.

File size limits depend on your plan · Drag & drop ready · Mixed file types welcome

A familiar browser workflowBatch processingNo installationSecurity & privacy
ONE CONVERSION OR A WHOLE WORKFLOW

Use the web tool now. Automate it when you are ready.

ConverterHQ is built for quick browser conversions and repeatable workflows. Choose the path that fits the work in front of you.

ADOC → XPMDirect upload · pair settings · async jobs · output download
# Contract-backed API v1 example. Pair-specific settings are validated by the capability schema.
# Local bytes always bypass the API process: create an owned File, upload to its signed URL, then submit the File ID.
API="https://sandbox.api.converterhq.io/v1"
FILE_JSON=$(curl -fsS "$API/files"   -H "Authorization: Bearer $CONVERTERHQ_API_KEY"   -H "Content-Type: application/json"   -d '{"filename":"input.adoc","content_type":"application/octet-stream","retention_seconds":3600}')
FILE_ID=$(printf '%s' "$FILE_JSON" | python3 -c 'import json,sys; print(json.load(sys.stdin)["id"])')
UPLOAD_URL=$(printf '%s' "$FILE_JSON" | python3 -c 'import json,sys; print(json.load(sys.stdin)["upload"]["url"])')
curl -fsS -X PUT "$UPLOAD_URL" --upload-file "input.adoc"
curl -fsS -X POST "$API/files/$FILE_ID/complete"   -H "Authorization: Bearer $CONVERTERHQ_API_KEY"   -H "Content-Type: application/json" -d '{}'

curl -fsS "$API/jobs"   -H "Authorization: Bearer $CONVERTERHQ_API_KEY"   -H "Content-Type: application/json"   -H "Idempotency-Key: example-adoc-xpm-001"   -d '{"tasks":{"convert":{"operation":"convert","input":{"file_id":"'"$FILE_ID"'"},"options":{"input_format":"adoc","output_format":"xpm","settings":{}}}}}'

# Official SDK convert helpers perform the same Files → signed storage → Jobs transport.

Contract-backed API v1 example. Pair-specific settings are validated by the capability schema.

AsciiDoc format

AsciiDoc at a glance

AsciiDoc

AsciiDoc began with Stuart Rackham's early-2000s toolchain and later gained broader ecosystem momentum through Asciidoctor and the ongoing Eclipse-led specification effort.

XPM format

XPM at a glance

XPM

Before today's relatively small set of mainstream consumer image formats dominated everyday use, desktop software, workstations, GUI systems, and early graphics tools produced many specialized raster formats with local importance.

How to convert AsciiDoc to XPM

1

Upload your AsciiDoc file.

2

Choose conversion settings and output format.

3

Download or share the converted XPM file.

Format comparison

Feature
AsciiDoc
XPM
File type

Not available

Not available

Extensions
  • .adoc

  • .asciidoc

  • .asc

  • .xpm

MIME type
  • text/asciidoc

  • image/x-xpixmap

Compression / quality

Not available

Not available

File size characteristics

Not available

Not available

Compatibility

Not available

Not available

Editability

Not available

Not available

When to use each format

When to use AsciiDoc

  • authoring
  • review and collaboration
  • distribution
  • Balances source readability with richer semantics than basic Markdown variants.

When to use XPM

  • capture ingest
  • editing
  • web or print delivery
  • Important for long-tail compatibility and archival conversion.

FAQs

Why convert AsciiDoc to XPM?

Choose XPM as target when maintaining or restoring X11-era icon assets or other historical Unix interface graphics.

What changes when converting AsciiDoc to XPM?

Convert to XPM when maintaining or restoring X11-era icon assets or other historical Unix interface graphics. It is useful where text-based icon compatibility matters more than modern compression.

What should I review after converting AsciiDoc to XPM?

After conversion, review these destination checks: Open converted output in ImageMagick and verify behavior on real samples; Compare output against the expected depends quality profile; Poor fit for modern mainstream publishing.

How can I keep quality stable in AsciiDoc to XPM conversion?

Run representative samples, keep settings deterministic, and monitor these risks: Tool support can be uneven and workflow-specific; Poor fit for modern mainstream publishing; Validate destination compatibility before large-batch conversion.

Format resources

AsciiDocXPM