Skip to main content

JSON-Resume

Generate a polished DOCX resume from strict, structured JSON.

json-resume validates your resume data before rendering, applies a stable Word layout with explicit paper sizes, and provides both a command-line tool and Python APIs. It is designed for repeatable resume generation in local scripts, automation, and backend services.

Install

python -m pip install json-resume

The package installs its DOCX and PDF-related Python dependencies together. PDF export uses local Microsoft Word through docx2pdf.

Command line

Create a JSON resume, then generate a DOCX:

json-resume resume.json

By default, output is written to output/resume.docx under the current working directory. Common options:

json-resume resume.json -o resume.docx
json-resume resume.json --pdf
json-resume resume.json -o resume.docx --force

--pdf additionally writes a sibling PDF after DOCX generation. --force is required before replacing an existing DOCX or PDF.

Python API

Use the file-level API in scripts and automation:

from resume_generator import render_json_file_to_docx

output_path = render_json_file_to_docx(
    "resume.json",
    "resume.docx",
)

print(output_path)

Use the in-memory API in HTTP services or other integrations:

from resume_generator import render_json_to_docx

docx_bytes = render_json_to_docx(data)

Both APIs use the same strict validation and rendering core as the CLI. Validation failures raise FieldError with a precise JSON source path.

JSON contract

The top-level JSON object must contain exactly paper_size, basics, and sections.

{
  "paper_size": "Letter",
  "basics": {
    "name": "Example Candidate",
    "contacts": [
      {
        "label": "candidate@example.com",
        "href": "mailto:candidate@example.com"
      }
    ]
  },
  "sections": [
    {
      "title": "Experience",
      "entries": [
        {
          "title": "Example Organization",
          "position": "Analyst Intern",
          "location": "New York, NY",
          "start_date": "2025-06",
          "end_date": "Present",
          "bullets": [
            "Completed a fact-supported contribution."
          ]
        }
      ]
    }
  ]
}

Supported paper sizes are A4 and Letter. paper_size controls the Word page size only and does not translate content.

Read the full JSON contract, examples, and usage guide.

Metadata

Release files for json-resume 1.1.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for json-resume 1.1.4
File Size Uploaded
json_resume-1.1.4.tar.gz 22.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for json-resume 1.1.4
File Interpreter ABI Platform
json_resume-1.1.4-py3-none-any.whl Python 3 none any Details

Total release size: 44.0 kB

Release files / json_resume-1.1.4.tar.gz

Download URL json_resume-1.1.4.tar.gz
Size 22.0 kB
Tags Source
SHA-256 checksum
How to use checksums
57de95b50a6b3902fcf37923ad731270e85eef1c806cb7ec7bc5a4ba62bde21f
BLAKE2b-256 checksum
How to use checksums
e0678ff37d3e2767650abf6ba503bb3f956028520dd4a4d6d342adb2bca1eb74
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 29, 2026.

Transparency log

Release files / json_resume-1.1.4-py3-none-any.whl

Download URL json_resume-1.1.4-py3-none-any.whl
Size 21.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0d092312b61aa1d495bd55a028a6af58d065b4e3e182f070df6ff990ad5909ac
BLAKE2b-256 checksum
How to use checksums
fcc585e0d0c85b4ec067e54ff56262c17f44789561ba2b16fe3228588569cad6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 29, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.1.4 This release

2 release files

1.1.3

2 release files

1.1.2

2 release files

1.1.1

2 release files

1.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page