Skip to content

Convert anything, at global scale.

300+ formats and automation APIs that feel instant.

CONVERT

From

To

IMAGEAsciiDoc PGX

Convert AsciiDoc to PGX

Convert AsciiDoc to PGX 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 → PGXDirect 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-pgx-001"   -d '{"tasks":{"convert":{"operation":"convert","input":{"file_id":"'"$FILE_ID"'"},"options":{"input_format":"adoc","output_format":"pgx","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.

PGX format

PGX at a glance

PGX

These formats persist in engineering, compression research, and conversion-tool contexts where simple sample storage or adjunct technical representation is useful.

How to convert AsciiDoc to PGX

1

Upload your AsciiDoc file.

2

Choose conversion settings and output format.

3

Download or share the converted PGX file.

Format comparison

Feature
AsciiDoc
PGX
File type

Not available

Not available

Extensions
  • .adoc

  • .asciidoc

  • .asc

  • .pgx

MIME type
  • text/asciidoc

  • image/vnd.jpeg2000

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 PGX

  • capture ingest
  • editing
  • web or print delivery
  • Useful for technical sample interchange and tooling.

FAQs

Why convert AsciiDoc to PGX?

Choose PGX as target when a technical imaging or codec workflow expects grayscale component data in a simple specialist format.

What changes when converting AsciiDoc to PGX?

Convert to PGX when a technical imaging or codec workflow expects grayscale component data in a simple specialist format. It is useful for research, testing, and standards-oriented image processing.

What should I review after converting AsciiDoc to PGX?

After conversion, review these destination checks: Open converted output in codec tooling and verify behavior on real samples; Compare output against the expected depends quality profile; Not intended for mainstream publishing or editing.

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

Run representative samples, keep settings deterministic, and monitor these risks: Sparse everyday application support; Not intended for mainstream publishing or editing; Validate destination compatibility before large-batch conversion.

Format resources

AsciiDocPGX