devbio
FeaturesExamplesMarketplaceToolsBlogsPricingFAQ
Sign inClaim your slug
All free tools

JSON Resume converter

Paste a jsonresume.org schema file and we generate a full devbio. Go the other way to export your bio as a portable JSON Resume. No signup, runs entirely in your browser.

JSON Resume input
Output
// Drop a JSON Resume on the left, hit Convert →

On this page

  • What is JSON Resume
  • How devbio maps the schema
  • What we don't map (yet)
  • FAQ
Guide

The JSON Resume schema, and why it matters

JSON Resume is a community standard for representing a resume as structured JSON. One source file, many renderers — your resume can be themed as a PDF, as a Hugo site, as a LaTeX doc, as anything that can read the schema. It's the closest thing the developer community has to a portable career file format.

What is JSON Resume

The schema (jsonresume.org) defines top-level keys for basics, work, education, skills, projects, , , , , , , and . Each is either an object or an array of objects with predictable shapes.

Done converting?

Publish your bio in 60 seconds.

Claim your slug and we'll pre-fill your editor with the components above. You can rearrange, tweak, then publish.

devbio.me/
devbio

The developer-first bio platform.

© 2026 devbio.me

Product
ComponentsExamplesMarketplaceResume builderPricingBlogs
Free tools
All toolsOpen Graph previewerMRR calculatorUsername availabilityTech-stack badges
Company
Twitter
volunteer
publications
awards
certificates
languages
interests
references

The win: tooling. There are dozens of themes, a CLI that compiles to PDF or HTML, and a small ecosystem of community renderers. Your file works everywhere; you don't lock yourself into one resume-builder's database.

How devbio maps the schema

The conversion is a 1:1 wherever possible:

  • basics.name → basic-info.name
  • basics.label → basic-info.tagline
  • basics.summary → about.body
  • basics.image → avatar.imageUrl (mode: image)
  • basics.location → basic-info.location (joined "city, region, country")
  • basics.email / url / profiles → links.items
  • skills → skills.items (names + keywords, flattened)
  • work → work-experience.items
  • projects → projects.items

The reverse direction is symmetric: every devbio component that has a JSON Resume equivalent gets one. Devbio-only fields (e.g. component versioning, custom heading overrides) are dropped on export.

What we don't map (yet)

JSON Resume covers ten top-level sections; devbio currently has eight active components. The unmapped ones — volunteer, publications, awards, certificates, languages, interests, references — don't have a 1:1 devbio component yet. When we add the matching components, they'll start round-tripping. Until then they survive on export (we preserve unknown keys) but show up as plain text fields on import.

FAQ

Will my data leave the browser?
No. The converter runs entirely client-side — there's no API call, no database write, no analytics on the input. Reload the tab and the data is gone.
Which JSON Resume version do you target?
v1.0 — the most recent stable. Older v0.x files might import with some fields ignored; the structure changes are small enough that you can usually hand-patch the JSON.
Can I sync my devbio with a live jsonresume.org registry entry?
Not yet. Today the converter is a one-shot. When the JSON Resume API stabilises around its auth story, we'll add a sync button.
My JSON has typos. Will it import?
We try to fail gracefully — invalid fields get skipped, parse errors show with the JSON.parse line/column. The strictness is on you, not on us.
GitHub
Privacy
Terms