How to Create a Resume Link Instead of an Attachment

How a resume link works

A resume link is a URL that opens your resume in a browser. You paste it into an email, a direct message, a proposal or a form field instead of attaching a file.

The main advantage is that the link can stay the same while the file behind it changes. If you fix a typo or add a new role, you replace the file. Then everyone who has the link sees the current version.

In short, put your resume PDF (or a one-page resume site) on a service that gives it a stable URL. Google Drive is the fastest route. GitHub Pages, Cloudflare Pages or Netlify give a cleaner address. Test the link on a phone and in a private window. Decide who can open it. When an employer asks for the file, continue to attach it.

• Time needed: about 10 minutes for a finished PDF
• What you need: your resume as a PDF, and a Google, GitHub, Cloudflare or Netlify account
• Result: a stable resume URL that you can reuse and update

Why share your resume online with a URL?

Each attachment creates a separate copy. With a link, you can fix a mistake, and earlier recipients do not keep the old version.

Links also work where attachments are awkward or impossible:

• LinkedIn messages and social profiles
• Freelancer proposals and marketplace profiles
• Email signatures
• Personal websites and portfolios
• QR codes on business cards
• Application forms with a website field

In Pew Research Center’s 2025 survey, 91% of US adults had a smartphone. For this reason, expect some people to open your resume on a small screen. A browser link removes the download step. But the resume itself must still be readable on a phone.

PDF resume link or simple resume site?

First, decide whether the link shows your existing PDF or a small HTML page. Each option suits different situations.

Consideration	PDF resume link	Simple resume site
Setup	Upload one finished PDF	Upload a folder with index.html, styles and a PDF
Layout	Keeps the designed page exactly	Adapts more easily to phone screens
Downloading	The document is already downloadable	Add a “Download PDF” link
Editing	Export and replace the PDF	Edit the page and publish again
Best use	Formal applications and quick sharing	Consultants, founders, designers and portfolio-led roles

A PDF keeps its layout on all devices and printers. This makes a PDF resume link a safe default. A resume site gives you room for selected work, case studies or contact links. But keep it restrained. A hiring manager still needs to find your experience, dates and contact details quickly.

For example, a financial consultant can share a conventional two-page PDF. A product designer can publish a responsive page with three case-study links and a PDF download. Neither option is better in general. Choose the one that makes less work for the person who reads it.

Option 1: Share the PDF from Google Drive

If you already use Google Drive, this is the fastest route. The link is long and opens in Google’s file viewer. But it works on any device.

1. Upload the PDF to Google Drive. Give it a clear name such as alex-morgan-resume.pdf.
2. Select the file. Click Share.
3. Under General access, change Restricted to Anyone with the link.
4. Keep the role as Viewer.
5. Click Copy link. Then click Done.

Google’s sharing instructions cover the same steps on mobile.

To update the resume later without changing the link, do not upload a second file. Select the existing file. Open the More menu. Choose Manage versions, and then Upload new version (Google’s steps). The file keeps its place and its link. The URL that you already sent now opens the new version.

This option has limits. The URL is long and looks anonymous. The page shows the Google interface. You also see no record of anonymous opens. If any of these limits is a problem, use your own resume URL instead.

Option 2: Host the resume on its own URL

A static host (a service that serves finished files) gives you a short address such as alex-morgan.pages.dev. Later, you can add your own domain. Start with a folder like this:

alex-morgan-resume/
  index.html
  alex-morgan-resume.pdf

If you only want the PDF, a tiny index.html is enough. With it, the root URL shows a page and not an error. The download is one tap away:

<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <title>Alex Morgan | Operations Consultant</title>
</head>
<body style="font-family: system-ui, sans-serif; max-width: 40rem; margin: 2rem auto; padding: 0 1rem;">
  <h1>Alex Morgan</h1>
  <p>Operations consultant. Email: alex@example.com</p>
  <p><a href="alex-morgan-resume.pdf">Open the resume (PDF)</a></p>
</body>
</html>

Then publish the folder on one of these hosts.

Cloudflare Pages (drag and drop)

1. In the Cloudflare dashboard, open Workers & Pages.
2. Select Create application, then Get started, then Drag and drop your files.
3. Enter a project name such as alex-morgan. It becomes the address alex-morgan.pages.dev.
4. Drag in the folder (or a ZIP of it). Select Deploy site.

Cloudflare’s Direct Upload guide has the details. To update the resume, open the project. Select Create a new deployment. Choose production. Upload the folder again. The address stays the same.

Netlify Drop

1. Sign in to Netlify.
2. Open Netlify Drop. Drag the folder onto the page.
3. To get a readable address such as alex-morgan.netlify.app, change the project name in the project configuration.

To update the resume, open the Deploys page of the project. Drag the new folder onto the dropzone at the bottom of the page (Netlify’s deploy docs).

GitHub Pages

1. Create a repository named <your-username>.github.io.
2. Use Add file and Upload files to add index.html and the PDF.
3. Open Settings, then Pages. Under Build and deployment, set Source to Deploy from a branch. Choose your main branch.
4. Visit https://<your-username>.github.io. Changes can take up to 10 minutes to appear (GitHub’s quickstart).

On GitHub Free, the repository must be public. The resume file is then also visible in the repository itself. Remove anything that you do not want on a public web page.

Choose a readable resume URL and page title

Choose a resume URL that looks deliberate. An address such as alex-morgan.pages.dev or resume.alexmorgan.com is easy to recognize and type. A random project name or resume-final-v7-new is not.

Use a page title that identifies the person and the work:

• Alex Morgan | Operations Consultant
• Nina Chen | Senior Product Designer
• Sam Rivera | Fractional Finance Lead
• Taylor Brooks | Full-Stack Developer

Name the file the same way, for example alex-morgan-operations-resume.pdf. Avoid spaces in file names. Also avoid final, latest and new in file names. The stable link already points to the current version, so those words age badly.

For example, a freelance copywriter can pitch with riley-park.netlify.app. Six months later, the copywriter replaces the resume. The links in emails, profiles and QR codes on business cards do not change.

Test the resume URL on mobile and desktop

A PDF that looks good in your editor can be uncomfortable on a phone. A two-column resume with eight-point text opens. But the reader must pinch and zoom all the time.

Before you share the link, test these items:

Item	What to test	Why it matters
First screen	Your name, role and contact path appear quickly	The reader sees at once whose resume opened
Text size	Body text is readable without constant zooming	Small type creates friction on phones
Navigation	Scrolling, PDF controls and links work	Broken controls can hide experience or projects
Downloads	The PDF downloads with a useful file name	Recruiters can save or forward it
Links	Email, LinkedIn, portfolio and project links open correctly	A typo can block the next step
Privacy	No home address, signatures, ID numbers or hidden comments	Anyone can copy public content

Test on a phone, on a desktop browser and in a signed-out private window. If you can, ask someone on another network to open the URL.

For a PDF link, test both the browser preview and the downloaded file. For a resume site, test narrow screens, keyboard navigation and text selection. Make sure that someone can find your current role, recent experience and contact information in 30 seconds.

Choose who can open it: public, password or email gate

Public access has the least friction and suits profiles, networking and broad job searches. A gate asks the reader for a password or an email address before the page opens. It adds a step for the reader but gives you more control.

Access	How to set it up	Good fit	Tradeoff
Public	Any of the options above, as published	LinkedIn, personal sites, broad applications	Anyone who gets the URL can forward it
Password	Netlify password protection (needs a paid plan, see Netlify’s docs) or Vercel Password Protection (Pro or Enterprise, see Vercel’s docs)	Targeted searches, material for limited distribution	The reader must keep track of a password
Email gate	Cloudflare Access in front of a Cloudflare Pages site, with the One-time PIN login	Consulting introductions and direct outreach where identity matters	The extra step can reduce opens
Named Google accounts	Google Drive with General access left on Restricted, then add people by email	A few known reviewers	Works best when the reader has a Google account

The email gate works like this. You allow specific addresses (the Emails rule) or a whole company domain (Emails ending in). The visitor types an email address. Cloudflare sends a code only to allowed addresses. The code expires after 10 minutes (One-time PIN docs).

Cloudflare Zero Trust has a Free plan. But onboarding still asks for payment details. Our Cloudflare Pages password protection guide shows how to protect the pages.dev address and a custom domain.

On GitHub Free, GitHub Pages has no password or email gate. Private Pages sites need GitHub Enterprise Cloud.

A noindex tag keeps a page out of Google results. But it does not stop anyone who has the URL from opening the page. The tag controls search, not access.

See whether the resume was opened

Be careful with what “opened” means.

• Anonymous counts: you can turn on Cloudflare Web Analytics for a Pages project under Metrics (how to enable it). It shows page views and visitors, not who they were.
• Email gate logs: if Cloudflare Access is in front of the site, the Access authentication logs list each login. They are in the Zero Trust dashboard and show the email of the user and the time.
• Document tracking tools: if you want reading data for each viewer of a PDF, a document-sharing service fits better than a web host. Papermark has a “Require email to view” setting and an email notification for each view (link settings). DocSend has a similar “Require an email to view” setting.

An anonymous visit does not tell you which employer or person opened the resume. Offices share IP addresses. Link scanners open URLs automatically. One person on a phone and a laptop looks like two visitors. Only an email gate or a sign-in ties a visit to an address.

Share the resume without creating friction

Label the link clearly. A bare URL can look suspicious.

Good examples:

• Resume: https://alex-morgan.pages.dev
• My current resume is here, with a PDF download on the page.
• Here is the resume and the project work I mentioned in my proposal.

When the instructions allow it, include the PDF attachment and the browser link. The attachment is for formal processing, and the link stays current.

A consultant can send a gated resume link after a discovery call. Then the consultant can use the access log to time a follow-up. For example, if the resume opens on Tuesday, the consultant sends the promised case study on Wednesday. The log shows that an allowed address signed in. It does not show how closely the person read the resume.

Shorten the URL only when space is tight. A readable domain gives context. If the link has a password, do not post the password in the same public place as the link.

Update your resume without changing the URL

1. Export the revised resume with the same file name and path as the current one.
2. Replace the file in the same place:
   • In Google Drive, use Manage versions.
   • In Cloudflare Pages, use Create a new deployment.
   • In Netlify, use the Deploys dropzone.
   • In your GitHub repository, upload the new file over the old file.
3. Open the original URL in a private window. Make sure that the dates, links, layout and download are correct.

For example, someone shares the URL with 20 contacts. After a promotion, certification or new contract, that person updates the file one time. Every existing link stays valid.

Keep one URL for ordinary edits. Create a second URL only for a different resume. For example, you can have one version for engineering roles and another for technical writing.

Keep dated source copies on your own computer, for example resume-source-2026-07.docx. The published file keeps its simple name. After each update, refresh the page in a private window. Browsers and caches can show the old file for a short time.

When an attachment is better than a resume link

Follow the employer’s process. If an application asks for an uploaded PDF or DOCX, provide it. A link is a supplement, not a substitute.

Use an ordinary attachment when:

• The job portal has a required resume upload field
• The employer explicitly asks for a PDF or DOCX attachment
• An applicant tracking system (software that sorts job applications) needs to read the document automatically
• The recipient works in an environment that blocks external links
• The employer must keep an exact record of what you submitted
• Internet access can be unreliable during the review

An attachment is a snapshot of what you sent on that date. Where that record is important, the employer can refuse a link that can change.

Often the best answer is both. Attach a clean, text-based PDF. Put the live URL next to your signature or portfolio link. Keep the PDF reasonably small. Use selectable text, not a full-page image. Avoid layouts that confuse software that reads resumes automatically.

Never replace a required attachment with a link. When you follow the instructions, you show judgment. No hosting setup can rescue an incomplete application.

A docs portal with Ask AI
and support tickets

Connect a repository, or describe your product to start. Each docs site has search, Ask AI, an API console, an MCP server and support tickets.

• Publishes from GitHub on every push
• Works with Mintlify repositories
• API console from your OpenAPI file
• MCP server and llms.txt for AI agents
• Ask AI and support tickets
• Analytics for people and AI agents

Start Free→ Questions? Ask AI in our docs

No card required.