1. LandOffer
  2. Blog
  3. All articles
  4. Cake Resume Builder Review: Versions, PDF Watermarks, and Shared Resume Pages

Job search

Cake Resume Builder Review: Versions, PDF Watermarks, and Shared Resume Pages

Distinguish one editable resume, retained PDF versions and shared-page access before paying for more resume slots.

10 min readLandOffer team

Cake is worth trying if you want to build one resume and can accept its free-plan branding. For a tech applicant maintaining several role-specific versions, the more important question is how many resumes remain editable, what each exported file contains, and which shared link a recruiter can actually open.

Its current Basic arrangement allows one resume per account. Premium adds unlimited resumes and branding removal, but cancellation eventually restricts editing to the earliest-created resume. Downloaded PDFs preserve delivery copies; editable Cake documents let you revise the source. Track both separately.

This review checks current Cake help and pricing as of October 14, 2026. We read the public instructions and rendered pages; we did not create an account, export a resume, change privacy settings, or purchase a plan. You can browse recent roles on LandOffer.ai to choose target applications, then check their requirements and decide which need distinct resume versions before paying for more slots.

A single editable resume at a worktable leads to several carefully labelled application PDFs, illustrating the difference between an editor slot and archived files.

Start with the one-resume boundary

Cake's current pricing page lists one resume for Free and unlimited resumes for Premium. Its February 24, 2026 help article describes a Basic workaround: export the existing resume, delete it to free the slot, and create another from a sufficiently completed profile. That sequence replaces the one active document; it does not keep several versions editable at once. Cake pricing, Multiple-resume guide

A PDF backup preserves what a reader sees. It should not be treated as proof that you can restore every editable block, layout setting, or link identity after deleting the original. This review did not test deletion or restoration. Before replacing your only document, keep your underlying text and application notes somewhere you can revise independently.

For someone sending substantially the same resume to a small number of roles, one editable document may be sufficient. For someone alternating among frontend engineering, full-stack work, and software QA, repeated replacement introduces a coordination task: which source version is in the editor, which file went to which employer, and whether an older shared page still represents the intended application.

Paying for more slots can reduce that coordination burden, but it does not make the versions factually correct. Preserve the same employers, dates, project ownership, and results across all variants. Change emphasis to match the role rather than adding experience that appears only in one job description.

Worked example: three versions from one evidence pool

The following is a fictional planning exercise, not documents created in Cake. Ren has a campus web project containing React forms, input-validation work, and a Playwright test suite. Ren implemented the form validation, worked on form-to-API integration, and wrote test cases; a teammate configured the deployment environment. The evidence pool does not include ownership of production infrastructure.

Ren has three target applications. The completed ledger below records what each planned local PDF would emphasize and which claim must stay out.

Target application Planned local file Evidence emphasized Claim excluded
Frontend role FE-21 ren-frontend-v3.pdf React form behavior and input validation Deployment-environment ownership
Full-stack role FS-08 ren-web-project-v2.pdf Form-to-API integration work Ren can explain Untested backend scaling claims
QA role QA-14 ren-qa-v4.pdf Playwright cases and documented failure reproduction A fabricated test-coverage percentage

These are proposed filenames and fictional application identifiers. Ren's source notes include work on the form-to-API integration, so that emphasis is supported; the ledger does not turn a keyword in the full-stack posting into new experience. Each file needs to be built and checked before it is sent.

On a one-slot Basic workflow, Ren decides to keep the frontend version as the active editable document while maintaining the other drafts in a separate local text source. The three named PDFs are a delivery plan, not evidence that the free account holds three editable resumes. If Ren later needs to alternate quickly between all three layouts inside Cake, multiple editable documents become a concrete reason to evaluate Premium.

Ren records which document was created first before relying on post-cancellation editing, so the version needed next is not accidentally left without editing access. The version most recently used is not necessarily the earliest-created one. That distinction matters if the most useful future source is a later document.

The ledger prevents an easy application error: uploading the QA file to a frontend role because it happened to be the last download. It also provides a place to record the actual sent filename after applying, without assuming that a future editor change updates a previously attached file.

Separate the Cake mark from printing headers

Cake's February 2026 export guide says Basic PDFs display a Cake watermark and Premium can remove it. The same guide separately describes disabling browser printing headers and footers to remove items such as the date, URL, or page numbers. Changing printing options does not establish removal of the plan-dependent mark. Export and printing guide

Inspect the actual output you intend to submit. If a free branded PDF is acceptable for your purpose, a paid upgrade may not be necessary. If you require an unbranded deliverable, compare the paid cost with the value of that requirement before building many versions around it.

Do not use a screenshot of the editor as proof of the exported PDF's appearance. Check the header area, footer area, page count, and links in the downloaded file. This review did not produce a Basic or Premium PDF, so it does not claim a measured watermark size, position, or rendering quality.

The branding question is also separate from ATS compatibility. Removing a mark does not establish that an employer's parser will correctly extract your dates, skills, or project headings. Follow the employer's requested format and inspect any application preview it provides.

Treat A4 page breaks as an export check

Cake's export guide describes default A4 break positions shown by red dashed lines, and says adjusted breaks take effect in the downloaded PDF. That is a specific reason to inspect the final file rather than only the online page. Export and printing guide

For a technical resume, check whether a project heading is separated from its bullets, a technology list wraps into an unrelated entry, or an employer and its dates land on different pages. Shorten or move a block when the break obscures the relationship between the evidence and the heading.

If an application asks for another paper size or a particular upload format, check the available export settings before assuming the A4 layout will meet it. This review did not verify a Letter-size export or a Word download. The documented PDF workflow should not be silently expanded into those capabilities.

Add the actual export date and final file check to each row of the version ledger after creating the files. For Ren, that means opening ren-frontend-v3.pdf and confirming that the React project stays together, then doing the same separately for the other two files. A good result on one version is not a layout test of all three.

Choose the resume audience explicitly

The current resume-specific help page describes three visibility options. Public links are accessible without login, with a separate search-indexing option. The default audience also includes paid users and employers on Cake. Link-only access removes platform browsing from the described audience, but anyone holding the link can still view without login. Profile privacy has its own settings. Resume privacy guide

Choose the option on the resume itself and read the wording shown in your account. Do not assume that a broad privacy description elsewhere on the site applies identically to your profile, resume, and portfolio. A setting that reduces discoverability does not identify one authorized recipient.

If you send a link to a recruiter, consider what would happen if it were forwarded. Keep the page suitable for the audience its access setting permits. That may mean using professional contact information and a public description of a project rather than private customer details or internal screenshots.

An application attachment and a shared resume link take different review paths, with an obsolete public link held aside for replacement.

Worked example: check the delivery route before sharing

This fictional example is a completed decision exercise, not a live Cake sharing test. Vega wants to apply to a role through an employer portal and separately obtain feedback from a mentor. Vega's prepared PDF is vega-platform-v2.pdf. An older public resume link appears in a draft message, while the intended resume audience has changed to link-only.

Delivery route Check completed in the exercise Decision before sending
Employer upload requesting a PDF vega-platform-v2.pdf is the intended version; the project heading and bullets stay together Attach that checked file when applying
Mentor feedback by resume page Intended audience is link-only; the mentor must receive the current link Use the current link and keep its contents appropriate if forwarded
Older public link in the draft message It predates the visibility change Hold the message until the current link replaces it

The help guide says changing from Public to another option invalidates the old public link. Vega therefore cannot rely on that earlier URL simply because it used to work. The guide's reference to an encrypted link does not establish authentication of a named mentor; its access description still allows link holders to view without login. Resume privacy guide

Vega checks the actual link in a signed-out browser before sending it, then checks the destination document's name and content. This is a proposed verification step, not a test performed for this review. If the employer requested a file, Vega uses that route rather than substituting a page URL without checking the instructions.

After submission, Vega records whether the employer received a file or a link. That preserves the difference between a fixed attachment and a page whose current contents or access settings may later change. The exercise does not assume the behavior of Cake's separately labelled PDF-link feature; check that specific output as well before using it.

Read the billing total and the editing end state

The public pricing page rendered dollar-denominated promotional amounts of $27.99 monthly, $50.39 billed quarterly, and $167.96 billed yearly during our check. A web extraction of the same URL showed pound-denominated amounts. These are observed page presentations, not a verified checkout quote, tax calculation, or promised renewal rate. Cake pricing

Compare the charged total with the period you need. A displayed monthly equivalent for an annual plan is not a one-month commitment. Before paying, read the checkout currency, total, billing interval, promotional terms, and renewal amount. This review stopped before checkout and did not purchase anything.

Cake's current pricing FAQ says cancellation leaves Premium active until the billing period ends. Its cancellation help states that resumes remain available for viewing, sharing, and downloading, while only the earliest-created resume stays editable after the upgrade ends. The help page also limits its seven-day refund request description to first-time subscribers. Cake pricing, Cancellation help

Preserving access to an old PDF is different from preserving the ability to edit every source document. If you expect to keep tailoring several resumes after a short paid period, plan the editable sources and creation order before cancellation. A refund request is also a separate process from stopping renewal; do not assume one automatically accomplishes the other.

When Premium solves a concrete problem

Premium addresses a concrete limitation when you need several simultaneously editable resumes or unbranded exports. It is harder to justify solely because a marketing page describes better recruiter visibility or a more polished presentation. Neither establishes an employment outcome for your application.

Cake also lists monthly AI credits, with different costs for different tools. Those allowances are separate from the number of resume documents. Check the activity you actually intend to use instead of interpreting unlimited resumes as unlimited AI analysis. Cake pricing

A useful trial of the free workflow is one truthful resume, an inspected PDF, and a deliberate audience choice. Add a paid plan only when you can name the limitation it removes. Keep a version ledger and check each employer's requested delivery route. Explore LandOffer.ai as you organize applications around those concrete document requirements.

Sources and Further Reading