Job search
Dunked Review: A Small Portfolio Site with Clear Project and Page Limits
A documented small-portfolio allowance, completed capacity inventory, and media-treatment record clarify what Dunked offers and what remains untested, including a direct pricing-page access failure.
Dunked’s appeal for a job seeker is a focused portfolio: a collection of projects, a few supporting pages, and media that helps explain the work. Its published Professional allowance—100 projects, 100 pages, and 1,000 images—is large enough to make content selection a more immediate question than capacity for many small portfolios. Compare your project, page, and media inventory with those separate allowances before paying for a larger plan.
That assessment also depends on how you present motion, link to demos, and control access. This review uses two completed fictional planning exercises to make those decisions concrete. Choose a target role from LandOffer’s recent job listings so the portfolio shows relevant evidence rather than simply everything you have made.

The published plans and the pricing check limitation
Dunked’s public pricing text lists Professional at $8 per month billed annually or $12 month to month. Agency is listed at $19 billed annually or $29 month to month, with unlimited projects and pages and a 5,000-image allowance. Both list custom-domain support, password protection, and advanced editing.
There is an important evidence boundary. On October 21, 2026, a readable retrieval of the official pricing page supplied those figures, while direct browser visits and an ordinary HTTP request returned a 502 error. A later browser attempt also failed. We preserved those results and have not established that a particular account or checkout would show the same offer. Recheck availability and the actual price before purchasing.
The upgrade guide clarifies that annual and monthly offers display prices on a per-month basis, but annual plans are charged once a year. At the documented Professional rates, that means $96 for a year versus $144 for twelve monthly payments, before any additional applicable charges. The calculation does not establish a refund entitlement or predict future renewal pricing.
We read public documentation and successfully inspected several help pages in the browser. We did not create an account, start a trial, upload files, build or publish a portfolio, connect a domain, or buy a plan. LandOffer publishes this review and offers job-search tools. The examples below are original specifications and calculations, not customer projects, editor tests, or hiring outcomes.
Projects, supporting pages, and usage are separate
The new-project guide describes a project title, description, media, optional role and date information, and an external project URL. That gives a candidate places to explain what the work involved and what they personally contributed. Add enough context for a reader to identify the task, your contribution, and what the image demonstrates.
Dunked also supports separate pages, such as an About or Contact page. Keep those supporting information pages distinct from project case studies when planning capacity. A project needs its own coherent story; a navigation item does not necessarily represent another piece of work.
The usage guide says accounts are limited by project, page, and media totals and documents a Usage view. A planning spreadsheet is useful, but the account’s actual usage is the check that matters after uploading. No account counter was inspected, so these examples do not verify how imported, embedded, thumbnail, or repeated assets count toward an allowance.
Agency’s advertised unlimited projects and pages also has an operational qualification: the pricing FAQ describes a displayed 999 limit and says to contact the service if more is needed. Treat that as a documented route for discussing higher capacity, not proof that the interface accepts infinitely many items. A job portfolio can be carefully edited well before reaching either plan’s project limit.
Worked inventory: six projects and room for later work
Eve is a fictional frontend developer preparing a portfolio around interface implementation and product-detail work. She has six project stories and wants four supporting pages: About, Resume, Contact, and Accessibility Notes. All project names and counts below are invented for this exercise; no files were uploaded or projects implemented for this review.
Her completed inventory assigns images to a purpose instead of keeping every screenshot:
| Project story | Planned images | What earns space in the case study |
|---|---|---|
| Form-review flow | 8 | Initial, invalid, corrected, and review states, with annotations. |
| Component library | 6 | Component variants and examples of where each belongs. |
| Search results interface | 5 | Filtering, empty results, and a readable comparison of layouts. |
| Accessibility repair | 4 | Before-and-after evidence with clear limitations on what was checked. |
| Dashboard layout | 3 | Information hierarchy and two representative screen widths. |
| Documentation interface | 6 | Navigation, content structure, and the example component’s behavior. |
The six projects total 32 planned images. Eve reserves two further images for supporting pages, making a paper inventory of six projects, four pages, and 34 image files. This counts planned uploads, not measured Dunked usage; it does not prove how the service would count a thumbnail or embed.
She also fills a growth scenario: three more projects, two more pages, and 18 more images. The combined inventory becomes nine projects, six pages, and 52 images. Against the published Professional allowances, that leaves numerical headroom of 91 projects, 94 pages, and 948 images, assuming the planned items are counted as expected. The totals and subtraction were checked locally; the actual Usage display remains untested.
Eve’s completed decision is to evaluate Professional rather than buy Agency for capacity she has not identified a need for. She records the conditions that would reopen the comparison: actual usage approaching an allowance, a substantially larger archive becoming part of the site, or an account-specific requirement not established by these public documents.
Eve uses the inventory to decide what each project should explain, rather than filling the available slots. She keeps the six stories as separate projects because each has a different question to answer. She removes redundant screenshots within a story rather than splitting one project into many items merely to make the portfolio look larger. Capacity is available; the reader still needs a clear route through the work.
Media support is specific, not a general application runtime
The project-media documentation lists JPG, PNG, and nonanimated GIF images, with a 100 MB file-size limit. It documents video embeds from YouTube and Vimeo and audio embeds from SoundCloud. A large upload allowance is not a recommendation to send the largest possible image to a visitor.
Keep a project’s explanation readable without depending entirely on external playback. A still image and caption can establish the relevant state or decision when a video does not load. A separate live application is also a separate dependency: displaying a portfolio page does not demonstrate that its linked backend, authentication, or data service works.
The documentation describes ordering media and adjusting thumbnails. Check the chosen image’s crop and whether labels remain readable in the active template. These are checks to perform on an actual site, rather than results demonstrated by this review. We did not upload the article’s own illustrations to Dunked or test any template’s media handling.
Worked media pack: replace unsupported motion with a clear sequence
Ben is a fictional candidate preparing one UI case study. His draft media list contains a workflow animation, two still images, a large diagram, a raw video, and an employer dashboard capture. The completed record below decides what belongs in a proposed pack; it does not claim that files were converted, accepted, or viewed in Dunked.
| Draft item | Review finding | Finished treatment decision |
|---|---|---|
| Animated GIF of a three-step flow | The documented image support excludes animated GIFs | Replace it with three planned PNG stills and explicit sequence captions. |
| PNG overview, assumed 2.4 MB | A documented image type below the stated maximum | Keep it in the proposed pack; inspect readability and actual upload separately. |
| WebP detail crop | WebP is not among the image types listed in this guide | Prepare a JPG or PNG from the original source rather than assume support. |
| PNG diagram, assumed 110 MB | Exceeds the documented 100 MB maximum | Hold it out of the pack until a smaller, readable version is prepared. |
| Raw MP4 walkthrough | The guide documents video embeds, not this direct-file upload route | Consider an appropriately accessible YouTube or Vimeo version; no video was uploaded. |
| Employer dashboard capture | Ben has not established permission to disclose it | Exclude it, including from password-protected sharing, until permission and suitable content are established. |
Ben completes the three replacement captions: “Choose an available option”; “Review the selected option before confirming”; and “Return to the form when the selection needs correction.” They describe the intended sequence without inventing a conversion improvement, a user-study result, or a production deployment.
Ben’s proposed core image pack contains five items: one overview, three sequence stills with the finished captions above, and one replacement detail crop. The oversized diagram is held back, the video remains optional, and the employer capture is excluded. That selection is a completed editorial decision, while preparation, rights verification, upload acceptance, and visitor playback are still pending.
He also writes the case-study scope statement: “This example explains the interface’s selection and review states. It does not establish a measured improvement in task completion.” Before using it, Ben would replace the fictional materials with his actual work and ensure that every claim matches the evidence he can show.
This pack gives a hiring reader something useful even without animation. It also prevents a file-format problem from silently becoming a claim that the portfolio builder is broken. The documented route, the prepared file, and the visitor’s actual result are three different things to verify.

Private-by-link and password protection are different controls
The project guide distinguishes On, Off, and Private visibility. Private projects are described as accessible through their direct URL while omitted from the portfolio homepage. That makes the label different from a requirement to enter a password. Do not assume that removing a project from the main index restricts everyone who receives its address.
Dunked’s password-protection guide describes a separate project password and shareable links that can bypass the password screen. Anyone holding a valid such link can gain access. Expiration and usage-limit options are documented, but we did not create or test a link, verify a recipient, or measure a protection boundary.
For application sharing, decide whether the reviewer should see the public portfolio or an intentionally restricted project, then check that exact route. Never send an account login as a way to grant visitor access. Password protection also does not grant permission to share confidential client work, private code, or employer data.
Trial, domain, and maintenance decisions
The pricing FAQ describes a ten-day trial without a credit card. That is a period to evaluate the service, not an ongoing free-publishing plan. It also says Dunked does not supply domain names: using a custom domain requires obtaining one separately. Include registration and renewal in your budget rather than treating custom-domain support as a domain purchase.
Use any evaluation period to answer a small set of concrete questions: can the selected template present your actual story, are the media readable, and can the intended visitor reach the relevant project? Check external demo and repository links separately. Public documentation alone cannot establish those results for your work.
Dunked is worth evaluating if you want a modest project-and-page portfolio and can maintain the content and supporting destinations. A need for a large archive may change the plan comparison; a need to run a complex application may instead require a separate hosting decision. Compare archive capacity and application hosting as separate requirements before choosing the subscription.
When the actual portfolio is ready, choose an opening from LandOffer’s latest jobs and share the most relevant work. Keep the project description accurate, the visitor route intentional, and the linked resume current. After sharing, distinguish a page that can be reached from evidence that a particular recruiter viewed or evaluated it; this review establishes no hiring outcome.
Sources and Further Reading
Checked October 21, 2026. Help pages were readable through ordinary retrieval and public browser inspection. The pricing text was retrievable through a separate public-source tool, while direct checks returned 502 errors. No account, trial, upload, payment, domain setup, sharing-link creation, or publication occurred.
- Dunked pricing: documented plans, trial, domain exclusion, and unlimited-capacity qualification.
- Upgrade account: billing-cycle explanation.
- Add a new project and create a page: content structure.
- Usage rates: account usage counters.
- Project media: supported media and presentation controls.
- Password protection: separate access controls and shareable links.


