MarkLayer

Product

MarkLayer featuresWhat's new in MarkLayerPricingSupport the projectAbout MarkLayerPrivacy

Guides

All guidesHow MarkLayer works, in plain EnglishWebsite feedback tools in 2026, twenty-one comparedHow to annotate a website, four waysHow to annotate a PDF for freeHow to annotate an image or screenshotThe best free website annotation tools in 2026, auditedCollecting website feedback without making anyone log inThe Markup.io price hike: what changed and what it costs nowMCP servers for bug reports and visual feedback, comparedGive your AI coding agent visual feedback from a live webpageSending MarkLayer annotations to Jira, Linear, Slack and moreOpen-source website annotation tools in 2026

Use cases

All use casesHow to get client feedback on a staging site without asking them to install anythingPoint an AI coding agent at a UI element on your local dev serverMarkLayer for Design ReviewMarkLayer for QA Bug ReportingMarkLayer for Client FeedbackMarkLayer for Remote TeamsMarkLayer for StudentsMarkLayer for EducatorsMarkLayer for ResearchersMarkLayer for Content CreatorsMarkLayer for MarketersMarkLayer for AgenciesMarkLayer for Freelance Web DesignersMarkLayer for Product Teams

Compare

All comparisonsMarkup.io review: MarkLayer is a free Markup.io alternativePastel vs MarkLayer: a free Pastel alternativeBugHerd vs MarkLayer: a free BugHerd alternativeAnnotateWeb vs MarkLayer: a free AnnotateWeb alternativeJam.dev vs MarkLayer: a free Jam.dev alternativeMarker.io vs MarkLayer: a free Marker.io alternativeUserback vs MarkLayer: a free Userback alternativeRuttl vs MarkLayer: a free Ruttl alternativeLoom vs MarkLayer: a free Loom alternativeHypothesis vs MarkLayer: a free Hypothesis alternativeUsersnap vs MarkLayer: a free Usersnap alternativestagewise vs MarkLayer: a free stagewise alternativeVolley vs MarkLayer: a free Volley alternativeSuperflow vs MarkLayer: a free Superflow alternativeFeedbucket vs MarkLayer: a free Feedbucket alternativeFigma vs MarkLayerHuddlekit vs MarkLayer: a free Huddlekit alternativeAtarim vs MarkLayer: a free Atarim alternativezipBoard vs MarkLayer: a free zipBoard alternativeWebvizio vs MarkLayer: a free Webvizio alternativeBugSmash vs MarkLayer: a free BugSmash alternativeYbug vs MarkLayer: a free Ybug alternativeSureFeedback vs MarkLayer: a free SureFeedback alternativeSimpleCommenter vs MarkLayer: a free SimpleCommenter alternativePageProofer vs MarkLayer: a free PageProofer alternative

Alternatives

All alternativesFree Markup.io alternative: 5 tools comparedFree Pastel alternativesFree AnnotateWeb alternativesFree Jam.dev alternativesThe best free Marker.io alternative, plus 3 more picksFree Userback alternativesFree Hypothesis alternativesBugHerd free alternative: 4 picks, 3 that cost nothingFree Ruttl alternativesFree Usersnap alternativesFree stagewise alternativesFree Loom alternativesThe closest free Huddlekit alternative, plus 3 more picksThe closest free SureFeedback alternative, plus 3 more picksThe closest free Atarim alternative, plus 3 more picksThe closest free Feedbucket alternative, plus 3 more picksThe closest free PageProofer alternative, plus 3 more picksThe closest free Superflow alternative, plus 3 more picksThe closest free Ybug alternative, plus 3 more picksThe closest free SimpleCommenter alternative, plus 3 more picks

MarkLayer for Freelance Web Designers

By Dean Rusin · Last updated: October 2026

A freelancer's review round has two people in it and no one to run the process, so the tool has to be the process. With MarkLayer, you paste a URL, send a link and the client comments on the page. There is no account to set up, nothing for them to learn, and nothing on the invoice. When the round is over, every comment is still pinned to the thing it was about, which is more than an email thread can say.

If you grow into a team with several clients at once, the agencies page covers how the same tool works when there are ten projects open instead of one.

Bottom line

For a freelancer, MarkLayer is the review tool that costs nothing and asks nothing of the client. You paste the staging URL, send one link, and the client comments on the real page from their own browser. No account for either of you, no extension for them, no monthly fee that only makes sense once you have a team. It looks like a process, which is the point.

On this page

The problem

Solo work means every revision round is yours to run. The client sends a reply-all with four screenshots and a line that says the spacing feels off, you spend twenty minutes working out which page they were on, and the next message says the first screenshot was from their phone. The feedback platforms built for this charge a monthly fee for a workspace you would use twice a month, and most of them want the client to sign up before they can type a word.

Why MarkLayer fits freelance web designers and developers who review work with one client at a time

How it works

  1. Paste the URL. Go to marklayer.app and paste the staging or live URL. The page loads inside the viewer with the annotation toolbar on top.
  2. Mark what changed. Pin a note on each section you want the client to look at, or leave it blank and let them react cold. Either way takes a minute.
  3. Send one link. Click Share and send the link by email or message. That is the whole onboarding.
  4. Client comments on the page. They open the link, click the spot they mean, and type. Replies thread under each pin, and you see them arrive in real time.
  5. Work the list. Mark each thread in progress and then resolved as you ship fixes. The client approves the ones they are happy with, and the round ends on the page where it started.

Frequently asked questions

Is it really free, or free until I need something?
There is one version and it is free. No trial, no seat count, no feature that unlocks on a paid tier. It is open source under Apache 2.0, so the price cannot change out from under a project you already shipped on it.
What does my client have to install?
Nothing. They open the share link in their browser and the comment tool is already loaded. On a phone they get a simplified bar with the comment tool and page navigation. The free Chrome extension is for you, and only when the site sits behind a login that the web app cannot reach.
Does this work on a password-protected staging site?
Not through the web app link on its own, because the page is fetched by MarkLayer's server without your cookies. Install the free Chrome extension, open the staging site in your signed-in tab, and annotate there. A reviewer on a protected site joins the room the same way from their own browser. [Staging feedback without an extension](/for/staging-feedback-no-extension) explains both paths.
Can I use it on the client's live site after launch?
Yes. The web app loads any URL the public internet can reach, so a post-launch tweak round works the same way as a staging review. The site itself is not modified. The annotations live in MarkLayer and are drawn on top.
What happens to the comments when the project is done?
They stay for 90 days after the room was last opened, and any visit resets that clock. If you want a record for the project file, fetch the room's JSON from marklayer.app/api/{id} before it goes quiet.
How does this compare to Markup.io or Ruttl?
Both are good and both put the useful parts on a monthly plan, and both are organised around a project workspace. MarkLayer has no workspace to join and no plan to pick. If you want project folders and version history, pay for one of those. If you want the client commenting within a minute of receiving a link, this is the shorter path. See [MarkLayer vs Markup.io](/vs/markup-io) for the detail.

Other use cases

Try MarkLayer

Paste any URL at marklayer.app and annotate the live page in your browser. No install, no account, no sign-up. Recipients of your share links don't need to install anything either.

Annotate a page

Or add the free Chrome extension for sites the web app cannot embed, such as pages behind a login.