Turn the résumé you already have into a portfolio page

The portfolio builder reads a résumé through the same specialists the other tools use. This page shows you what it would arrive with, lets you settle the design first, and then opens the builder with the document already read in.

ConxfolioPublished 2026-09-13

— the roles are already written.

A portfolio and a résumé hold the same material in two shapes. The résumé is a file somebody screens; the portfolio is a page somebody reads. Writing the second from scratch when the first already exists is duplicated work, and duplicated work is where the two versions start disagreeing with each other.

The portfolio builder reads a résumé through the same specialists the résumé builder and the letter use. This page shows you what that reading produces before you commit to it, which is the part the builder cannot show you until you are already inside.

What the sheet actually holds

The sheet is the builder's content surface: one row per thing a portfolio page can print. Your name, your headline, the introduction, the roles, the projects, the skills, the education, the certifications, the languages, and the links. The chain above lists all of them and marks which ones your document fills.

An empty row is information. It means the readers found nothing for it and refused to compose something, which is the same rule that governs every reader on this site. A field that fails their own check that it is a span of your document is dropped and counted rather than kept, so the count in the first receipt is worth reading before you go on.

The rows that matter most for a portfolio are the projects and the lines under your roles. A résumé written tightly for a one-page limit often carries three lines per role where a portfolio page has room for six. How many projects to show covers the judgement, and the piece on evidence you forgot you had covers where the extra lines usually come from.

Choosing the design before the content

The design chooser sits before the builder here on purpose. There are 20 authored designs across 6 directions, and they are not interchangeable skins: a cinematic design wants a short introduction and strong project images, an editorial one wants prose, a technical one wants runbook lines and numbers. Settling that first changes what you write.

Each of the six on this page is drawn by the product's own gallery route as the page loads, so the poster is the design rendering rather than a picture taken of it once. The full showcase has the other fourteen, at full width, with the filters. Choosing between two designs is the piece to read when two of them both look right.

Then the builder, with the document in it

The door at the end of the chain hands the text to the builder through the same import an uploaded file goes through. The builder then asks about every row before it prints anything: which roles to show, which projects, which sections to keep. Nothing is published, and nothing already saved on this device is altered.

That asking is the whole design of the thing. A page built by a tool that guesses reads like a page built by a tool that guesses. The questions the readers ask are where the accuracy comes from, and answering six of them takes about two minutes.

Publishing, and keeping it private

A portfolio stays a draft in this browser until you publish it. Publishing gives it an address here and costs nothing, including the address. You can also keep it unpublished and export the material, which is what most people do while they are still applying. The piece on publishing or keeping it private covers the trade, and choosing an address covers the handle itself.

Whatever you publish, check it at phone width before you send the link. Most first views of a portfolio happen on a phone, and a design that only holds together at 1440 is a design most readers never see properly. The phone guide covers what changes.

Where the portfolio sits beside the rest

A portfolio does not replace the file an employer asks for. It is the thing a link in your résumé header points at, which is why linking one from a résumé is worth doing properly rather than as an afterthought. And a portfolio is worth the ten extra minutes mostly when the work is visual, built, written or measurable. When a portfolio beats a résumé is honest about the cases where it does not.

If you want the file half of the application settled first, the export chain renders the PDF and reads it back through the checker, and the bundle chain is the résumé, the check and the letter in one sitting. A portfolio also carries a change of field further than a file does, which is where the career-change chain starts.