Resumake shut down. Here is how to edit your resume.
The form at resumake.io is gone, but the JSON it gave you is a standard file, not a private one. Import it here, edit it in a form with a live preview, and download the PDF. No LaTeX, no account, nothing to pay.
What happened to Resumake
Nothing is broken on your end. If you searched “resumake not working” or “is resumake down”, the answer is that the tool retired. Load resumake.io today and you get a short farewell note from Saad Quadri, the developer who built the site and ran it for years, where the form used to be.
The note is worth reading. There is no acquisition, no pivot to a paid plan, no domain squatter. He explains he is not in a position to keep working on it, thanks the people who used it, and asks for one thing on the way out: someone trustworthy to take the project over, on the condition that it stays free. Until that person shows up, the hosted editor is not coming back.
What survives is the thing Resumake was careful about. It never locked your content up. Every resume you built could be exported as JSON in the open JSON Resume schema, which means the file on your disk is still a working resume. It just needs an editor that speaks the same format.
- resumake.io
- Loads, but serves a farewell note where the form used to be.
- The resume form
- Gone. There is nothing to fill in and nothing to generate.
- Your exported .json
- Still completely valid. It is the JSON Resume schema, not a private format.
- Your exported PDF
- Still yours, and still parseable back into a form.
- The source code
- Still on GitHub at saadq/resumake.io, for anyone who wants to run it locally.
How to edit Resumake resumes after the shutdown
Three ways in, depending on what you still have on your disk. The first one is exact. The second is close. The third is a fresh start.
The best case. A direct schema mapping, field to field, with no parsing and no AI in the loop. Your bullets arrive exactly as you wrote them.
Upload it in the same import screen. A parser reads the document and fills the form, which gets you most of the way there. Read it over once before you export.
Start from a template with example content already in place, so you can see the layout before you type. Jake's is the closest in spirit to Resumake's single-column output.
Importing your Resumake JSON, step by step
- 1Find the file
Check your downloads for the .json Resumake exported, usually named resume.json. It does not matter how old it is; older field spellings are handled.
- 2Open the editor
No signup, no onboarding. The import screen is the first thing you see.
- 3Choose Import JSON Resume
Pick the JSON option rather than the PDF one, then select your file.
- 4Read the confirmation screen
Before anything is written, you get a list of every section coming in with counts, plus anything the layout will not print. No silent data loss, no guessing.
- 5Edit, then export
Your content lands in the form with a live preview beside it. Export a PDF when you are done, or export the JSON Resume file again to keep your own copy.
What carries over
A resume format is only as good as its edges, so here they are. This is the file the importer expects, and exactly what happens to each part of it.
{
"basics": {
"name": "Ada Lovelace",
"email": "ada@example.com",
"website": "https://ada.example.com",
"profiles": [
{ "network": "GitHub", "url": "https://github.com/ada" }
]
},
"work": [
{
"company": "Analytical Engines Ltd",
"position": "Principal Engineer",
"startDate": "2019-03",
"endDate": "",
"highlights": ["Designed the note G compiler."]
}
],
"skills": [
{ "name": "Languages", "highlights": ["Assembly"] }
]
}Note the older spellings in this sample: work[].company, basics.website, skills[].highlights. Plenty of importers choke on those. This one reads them and tells you it did.
- Name, email, phone and website from basics, plus your summary.
- LinkedIn and GitHub, picked out of the profiles array by network or URL.
- Work history with company, role, location, dates and every highlight. A work[].summary becomes your first bullet rather than being dropped.
- Consecutive entries at the same company are merged into one entry with multiple positions, the way a promotion should read.
- Education with institution, degree, field, GPA and dates. Projects, skills, certifications and awards all map across.
- Dates in any shape the schema allows: 2019, 2019-03, 2015-06-01, an empty endDate for a current role.
- Sections these layouts have no place for: volunteer, publications, languages, interests, references.
- A profile photo, a headline label, and your street address from basics.location.
- Profiles beyond LinkedIn and GitHub, along with education courses and skill levels.
None of it is deleted. Everything in that list is stored with your resume and written back when you export the JSON again, so importing here and exporting later does not quietly cost you your publications. The import screen names each one before you confirm.
The same file goes back out
Resumake had a rule about this and it was the right rule: whatever you type belongs to you, and the tool should hand it back on request. Export JSON Resume sits next to Export PDF in the editor toolbar and downloads the same open schema you imported.
That matters more than usual right now. You are here because a tool you relied on stopped running, so the sensible thing to ask of the next one is how you leave it. The answer here is one click, in a format that any JSON Resume theme, any other importer, and a future maintainer of Resumake itself can read.
Where this is not a like-for-like replacement
Worth knowing before you spend ten minutes moving your resume across.
Resumake handed you the LaTeX source along with the PDF. This builder produces the PDF only. If maintaining a .tex file is the point for you, clone the Resumake repo or move to Overleaf instead.
You get Jake's, Modern Deedy, Awesome CV, Harvard and WSO, not Resumake's exact six. Jake's is the closest match to the single-column output most people used.
The free tier holds one resume and one lint report. At PDF export we ask for your email once so we can send a link back to your workspace, with a skip button beside it. Resumake never asked at all, and that difference is real.
If you would rather compare every option before committing, the Resumake alternatives guide judges five free tools against Resumake's own three rules, cons included, ours among them.
Frequently Asked Questions
What people ask after finding the farewell note at resumake.io.
›Is Resumake down?
The site loads, but the resume form is gone. resumake.io now serves a farewell note from Saad Quadri, the developer who built and ran it, explaining that he is no longer in a position to keep working on it. So if you searched 'resumake not working', nothing is broken on your end. The tool retired.
›What happened to Resumake?
Its developer retired it. resumake.io now serves a farewell note asking for someone trustworthy to take the project over, on the condition that it stays free. Until that happens there is no form to fill in. The source is still on GitHub, but the hosted editor is not running.
›Can I import my Resumake JSON?
Yes. Resumake's JSON export follows the JSON Resume schema, which this builder reads natively. Open the editor, choose Import JSON Resume, pick your .json file, and you get a confirmation screen listing exactly what is coming in and anything that will not be printed before anything is written. It is a direct schema mapping, not an AI guess, so nothing is invented and nothing is reworded.
›My Resumake JSON is a few years old. Will it still import?
It should. Older exports use pre-1.0 field spellings that break some importers: work[].company instead of work[].name, basics.website instead of basics.url, skills[].highlights instead of keywords, and a top-level certifications array. All four are read here, and the import tells you when it fell back to an older spelling. Loose dates like '2019', '2019-03' or 'Present' are handled too.
›I only have the PDF Resumake made. Can I still edit it?
Yes. Use the PDF option in the same import screen. That path runs a parser over the document and fills the builder with what it finds, so it is worth a read-through afterwards. If you have the JSON, always prefer it: the JSON path is exact.
›Where do I find my Resumake JSON file?
In your Downloads folder, usually named resume.json, from the last time you clicked JSON export in Resumake. Check any cloud drive you back downloads up to as well. If you never exported one, the site no longer runs the form, so use the PDF import path instead.
›Is this free?
Building and exporting a PDF is free, with no watermark on any template and no payment step. The free tier covers one resume and one lint report. Pro exists for people who keep several tailored versions and want full lint reports every month, but nothing on the Resumake path requires it.
›Do I need an account?
No. You land straight in the editor and can import, edit and download without signing up. At download we ask for your email once so we can send a link back to your workspace, and there is a skip button next to it. An account only matters if you want the resume saved across devices.
›Can I get my data back out?
Yes. Export JSON Resume gives you the same schema back as a .json file. Anything the file carried that this builder does not print, such as publications or references, is stored with the resume and written back into the export, so a round trip does not quietly delete parts of your history. That was Resumake's rule about lock-in and it is worth keeping.
›Is Resumake open source? Can I run it myself?
Yes. The project is still at github.com/saadq/resumake.io, and if you are comfortable with a Node toolchain you can clone it and run the editor locally. That is the only way to get the original app back today. This page is for the larger group who wants to edit a resume, not host one.
›Which template here looks most like Resumake?
Jake's. Resumake's output was single-column LaTeX with serif typography and tight section rules, and Jake's is the closest match in this builder: single column, dense, and the default recommendation on r/EngineeringResumes. Deedy, Awesome CV and Harvard are also available if you want a different look now that you are switching anyway.
Related reading
Longer pieces on the shutdown, the alternatives, and the templates.
Your resume is five minutes from editable again
Drop in the JSON, fix the bullet that has been bothering you, export the PDF. If you want a second opinion on the content while you are in there, the built-in linter reads it the way an ATS parser does.
