A portfolio link on resume can strengthen an application when the role asks for visible work. It can also waste space or create a bad surprise: a private page asks for permission, the first project is unrelated, or a client file appears without consent. The decision is not simply whether you have a website. It is whether the exact destination helps a stranger understand evidence for this particular vacancy.
This free guide uses an ordinary document editor, a browser and the final file. Choose the destination, write a readable label, protect confidential material and test the export. No paid portfolio service is necessary. Follow the employer's instructions, especially when a separate upload is required.
When a portfolio link on resume earns its place
Start with the vacancy rather than the existence of your website. A designer, writer, developer, researcher or photographer may need samples because the work itself is hard to judge from a job title. An operations candidate may also have a permitted process diagram or public report that demonstrates a relevant method. Yet a portfolio is not compulsory for every role. If the employer asks only for a concise resume and your public page contains weak or unrelated material, omitting it may be the better editorial decision.
Read the wording carefully. Some advertisements ask for a portfolio URL on the resume; others want a PDF upload, a separate website field or samples sent later. These are different submission routes. A current job listing distributed through Harvard Career Services explicitly says an application without a portfolio link on the resume is incomplete. That is a rule for that particular listing, not a universal hiring rule. Copy the actual instruction into your checklist and comply with it.
Use a relevance test before editing: can a visitor reach at least two pieces of work that answer the vacancy's real questions? Can they tell what you personally contributed? Are the samples current enough to represent your ability? If the answer is no, improve the destination first. A polished URL cannot compensate for an empty gallery, unexplained screenshots or projects whose ownership is unclear.
Choose one useful destination before choosing its label
A homepage can be appropriate when it immediately presents your best relevant projects. Otherwise link to a focused landing page or collection. The visitor should understand the field, see the strongest example quickly and have a clear path to deeper detail. Do not force someone through a biography, an account prompt, an unrequested download or several navigation menus before they reach the work. A single stable destination is easier to maintain across an application than four scattered links.
Select projects using the employer's tasks, not popularity on your own site. For a service-design role, one well-explained research-to-prototype case may be more useful than many visual mockups. For a writing role, lead with pieces that show the type of audience and editing responsibility named in the vacancy. For a technical role, explain the problem, your contribution, constraints and what is actually public; a code repository with no context can leave the reader guessing. If a project involved a team, name your part without taking credit for the whole output.
A simple page is enough. You can even use an accessible PDF or public folder if access is reliable and the employer accepts that format. What matters is not an expensive platform but a predictable path: title, short context, your role, the work sample and a plain explanation of what was learned or delivered. Harvard's portfolio-tools overview shows several possible formats; it does not make one tool mandatory. Keep the destination under your control as far as possible so the link does not vanish mid-search.
Where to put the link in a readable resume
For one general portfolio, the contact area near your name is usually the clearest place. Put it beside an email address and other essential contact details, not inside a decorative icon or image. Use a label such as “Portfolio: yourname.example/work” or “Selected projects: yourname.example/projects.” The exact wording can reflect the audience. A hiring manager should know what the link opens before clicking. Keep the line visually quiet so it does not compete with the experience section.
If only one project supports a specific achievement, a second contextual link may sit in the related project entry. Do not repeat the same site after every bullet. A resume is still a summary, not a directory. If the application form has a dedicated URL field, enter the destination there as requested; you may retain the resume link when it genuinely helps the file stand alone. If the employer asks for a separate portfolio attachment, prepare that artifact rather than assuming the resume link substitutes for it.
A visible, short address survives printing and gives the reader a fallback if clicking fails. A hyperlink on “portfolio” alone may disappear in copied text. A long tracking URL is hard to read and type. Prefer a stable address you control or a clean public profile URL. Avoid a QR code as the only route: readers on a phone cannot conveniently scan their own screen.
Make the resume and portfolio tell the same story
The link is a bridge to evidence, not a substitute for evidence in the resume. Keep the relevant role, skills and outcome understandable without a click. A reviewer may not open external sites, and some application systems strip hyperlinks. Under a project entry, write a short truthful description of the problem, your contribution and a result you can support. Then the portfolio provides depth. The resume should not say “led the redesign” if the case study says you were one contributor to a larger team.
Names and dates should agree too. If the resume calls a piece a 2025 freelance assignment, the public case study should not present it as a 2024 employee project. If the project was coursework, identify it as coursework. If a prototype was never launched, say prototype rather than production service. The point is not to remove every nuance, but to prevent a reader from finding two incompatible accounts of the same work. A free guide to showing freelance work covers this distinction in more detail.
A visitor should understand a project within a minute: what question it addressed, what you did, what constraints mattered and what artifact they are seeing. Avoid invented impact metrics, vague “end-to-end” claims or confidential screenshots used only to look impressive. For early-career applicants, a well-labeled class or personal project can be meaningful if the scope is honest; see the first-resume evidence guide.
Protect confidential projects and other people's data
Before publishing a client or employer project, check your agreement, workplace policy and the permissions attached to the files. Public availability elsewhere does not automatically give you permission to repost internal process notes, customer data, design assets or unpublished results. A blurred screenshot can still expose names, account details or a recognizable client workflow. When in doubt, ask for written approval for the exact material or use a description that does not reveal protected information.
You can demonstrate method without showing restricted work. Describe the type of problem, your responsibilities, a non-identifying constraint and the outcome that is public or safely general. If a case study needs numbers, verify them and check whether they are shareable. Do not invent substitute figures. Where even the client's identity is restricted, use a broad category only if it cannot identify the organization indirectly. A hiring conversation may permit a more detailed explanation under appropriate conditions, but the public internet is a different audience.
Protect colleagues and research participants too. Remove their names, faces, feedback and raw responses unless you have a clear right to publish them. Link permissions also matter: “anyone with the link” can make a supposedly private folder widely accessible once the resume is forwarded. A password may be suitable when explicitly allowed, but do not put a reusable personal password in a broadly shared resume. Agree on access with the employer when a controlled sample is required.
Test access as someone outside your account
Open the destination in a private browser window while signed out of the hosting service. Better yet, ask a trusted person on another device to open it without special instructions. Check the landing page, at least one project and any PDF or media file behind it. A page that works only for its owner is a common failure. Confirm that no login, permission request, expired share token or regional block interrupts the path. If the employer cannot reach the work, the attractive label is irrelevant.
Inspect the mobile layout and loading time over an ordinary connection. A huge video or image gallery may be difficult to review between meetings. Give videos captions or a short written description where useful; provide meaningful text around images so someone who cannot see the visual still understands the work. Avoid autoplay and pop-ups that hide the actual samples. Where a repository or interactive prototype is central, include a concise explanation of what can be assessed without installing software.
A temporary share, expiring preview or renamed folder can break after submission. Choose a stable path during the hiring process. If you reorganize your site, redirect and retest the old address. Record which URL you submitted with each vacancy so you can fix the right destination.
Verify the exact PDF or DOCX you will submit
In your document editor, create a real hyperlink and display a meaningful, reasonably short address. Export in the format the employer requests. Then reopen the exported file outside the editor and click the link there. The editor preview is not enough: export can change hyperlink behavior, line breaks and visible text. Copy the visible address from the file into a browser and check that it matches the intended destination. If the link wraps awkwardly, shorten the path or revise the contact line rather than shrinking all text.
Also test a plain-text copy of the contact area. This does not reproduce every applicant tracking system, but it reveals whether the address exists as selectable text rather than only inside an icon or image. Do not promise that a particular design will pass all systems. Employer instructions and the actual upload preview outrank general advice. The PDF versus DOCX guide explains how to choose the requested format without treating either extension as universally superior.
Check the filename and the application portal after upload. Some systems rename attachments or preview them differently. Make sure the current version, not an old draft, is attached. If the form asks for a portfolio URL separately, paste the same tested destination there and remove accidental trailing spaces. Save an unchanged copy of the submitted resume, the vacancy instructions and the destination URL. That record makes a later interview much easier to prepare for.
If the portfolio is unfinished, decide honestly
An unfinished portfolio does not automatically mean you should delay every application. If the employer does not ask for samples, a strong conventional resume may be enough. If samples are mandatory, make a small, honest collection that satisfies the instruction and test it before submission. Do not label a placeholder page “coming soon.” That turns a potentially useful link into evidence that the application was not ready. One complete, relevant case can be stronger than a gallery of half-written cards.
There are alternatives to a public site. A permitted PDF packet can work when the employer asks for an attachment, and a focused writing sample may be better than a broad portfolio for an editorial role. An academic CV or regulated application may have its own prescribed evidence format. Follow the requested channel rather than forcing everything into a link. If you have no shareable work because projects are confidential, explain relevant responsibilities on the resume and ask whether a redacted or private sample can be considered.
Before sending, perform a final human check: does the destination show work you are allowed to share, does the first screen connect to the vacancy, can an outsider open it, and does the exported resume describe your contribution accurately? If any answer is no, fix the destination or remove the link. The goal is not to maximize clicks. It is to give a reader a trustworthy route from a concise claim to evidence they can actually inspect.