free ux research templates | Mantlr

<!--

IMAGE: HERO (cover image, 1600×900)

RENDER: A 16:9 dark-mode horizontal "research pipeline" composition on #0E0F11 background. Five distinct phases shown left-to-right as connected stations: (1) "Discovery" with magnifying glass icon, (2) "Generative" with sketch/persona card icon, (3) "Evaluative" with checklist icon, (4) "Synthesis" with affinity-map cluster icon, (5) "Repository" with database/folder icon. Each phase tile shows a representative template thumbnail underneath (e.g., research plan, persona card, usability test script, affinity diagram, research repo dashboard). Thin connecting lines between phases with subtle arrows. Bottom-left: small label "Free UX research templates by phase — 2026" in mid-grey.

ALTERNATIVE: A single large laptop mockup displaying a research repository dashboard with multiple template cards visible (persona, journey map, interview script, usability test plan), against a dark gradient background.

FILE: /images/blog/free-ux-research-templates-2026-hero.png

ALT TEXT: "Free UX research templates every designer should have in 2026 — discovery, generative, evaluative, synthesis, and repository templates organized by research process stage"

-->

You are about to start a user research project. Maybe a usability study on a new checkout flow, maybe interviews to inform a redesign, maybe a competitive analysis before kickoff. You search for "free UX research templates" and the SERP delivers what every SERP delivers: 30 templates in a random pile, no clear way to know which template to use when, half of them gated behind email signups, half of them last updated in 2022 when "demographics-first personas" was still the default. None of them tell you when to use each template, what the 2026 best practice version actually looks like, or how the templates connect across the research process.

This guide fixes that. The free UX research templates that actually ship work in 2026, organized by what stage of the research process they serve: discovery, generative, evaluative, synthesis, and repository. Every template named with the source, the license, what it does well, and where the 2026 best practice has evolved past it. No template directory dumping. No "30 templates for everything" lists that don't help you pick the right one for Tuesday morning.

A note on the 2026 landscape before the list. Three shifts changed UX research practice in the last 18 months. Demographics-first personas are dead for B2B SaaS; the modern persona leads with role, responsibilities, jobs-to-be-done quoted verbatim from interviews, and decision criteria. AI agents joined the persona library as non-human users with their own success criteria and failure modes. Persona simulations — AI layered over real research transcripts so you can "chat" with the persona — became the working synthesis tool for senior designers. Templates that still lead with "age, location, gender, occupation" as the first persona fields are reading as outdated in 2026.

Skip to the comparison table for the short version. Read on for the reasoning behind each pick.

Mantlr curates the best free UX research templates in one place — organized by research phase, tool, and license so you know exactly which template to use on Tuesday morning.

Browse UX Research Resources on Mantlr →

Free UX research templates at a glance

|---|---|---|---|---|

All twelve templates are free for individual use; team and enterprise features typically require paid tiers of the parent tool (Miro Pro, Notion Plus, Figma Professional). Most cover the core research workflow without ever needing to upgrade.

How to read this list: the five research stages

Before the templates, the framework that makes the list useful. UX research moves through five distinct stages, each needing different templates and different mental models.

Discovery is the planning phase: what are you trying to learn, why does it matter, who are you talking to, what methods will you use. Wrong template at this stage produces unfocused research that wastes weeks.

Generative is the data-gathering phase: interviews, surveys, observation, contextual inquiry, ethnography. Templates here scaffold the conversations and observations themselves. Wrong template produces shallow data or biased questioning.

Evaluative is the testing phase: usability tests, prototype validation, A/B tests, design walkthroughs. Templates scaffold structured testing protocols that produce comparable results across participants.

Synthesis is the meaning-making phase: turning interview transcripts and test recordings into patterns, insights, and recommendations. Templates here are about visual sense-making (affinity diagrams, journey maps) and stakeholder communication (findings reports).

Repository is the storage and reuse phase: where insights live, how they are tagged, how teams find them six months later. Most teams skip this stage and re-do the same research every quarter as a result.

Pick templates from the stage you are in. Mixing stages (using a persona template during discovery, using a research plan during synthesis) wastes time and produces work that gets reviewed and rejected at the next phase boundary.

Discovery templates: plan before you research

1. UX research plan (Miro, Figma, or Notion)

Best for: Kicking off any research project, aligning stakeholders on scope and methods | Tool: Miro, Figma, or Notion | Source: Miro's free template (miro.com/templates/ux-research-plan/), User Interviews' research plan templates | License: Free with a free Miro or Notion account

A UX research plan documents what you are trying to learn, why it matters to the business, who you are recruiting, what methods you will use, what timeline you are committing to, and how you will share findings. It is the single document that prevents scope creep, stakeholder confusion, and the "we ran research but nothing changed" anti-pattern.

The 2026 version of a UX research plan adds three sections older templates skip: decision-readiness (which specific decisions this research will inform), null hypothesis (what would need to be true for us to not change anything), and synthesis cadence (how often during the research we will pause to look at what we have learned so far instead of waiting until the end).

What makes Miro's template the right starting point: it is the most-used template in the category, your stakeholders likely already know how to read it, and the Miro free tier covers individual use without limitation. The Notion alternative is better if your team lives in Notion documentation; the structure is the same, the medium is different.

Where it falls short: research plans written as documents rarely get re-read. The most-skipped step is sharing the plan with stakeholders before fieldwork begins and getting explicit sign-off. Without that step, the plan becomes scaffolding for the researcher rather than alignment with the business.

2. Competitive audit template

Best for: Pre-research grounding, understanding the existing solution space | Tool: FigJam, Notion | Source: Multiple Figma Community files | License: Free with a Figma account

A competitive audit is the structured look at what already exists in your problem space: how competitors solve the same problem, where they fall short, where they succeed, and what conventions users already know from those products. This is not "look at five competitors and copy their patterns." It is the structured analysis that informs your design decisions with evidence rather than instinct.

The 2026 version of a competitive audit includes screenshots, specific pattern documentation (what each competitor does at the moment that matters), accessibility notes (which competitors pass WCAG 2.2 contrast checks and which don't), and one explicit "what we will NOT do" column that documents conventions you reject and why.

What makes the FigJam version useful: visual side-by-side comparisons of screenshots with annotations. The Notion alternative is faster for text-heavy analysis but loses the visual comparison power. For most competitive audits in 2026, FigJam wins on the visual side, Notion wins on the documentation side.

Generative templates: gather data

3. User interview guide

Best for: Semi-structured user interviews during generative research | Tool: Notion, Google Docs, Xtensio | Source: User Interviews' research field guide, Xtensio's free user interview template | License: Free with free Notion, Google Docs, or Xtensio account

A user interview guide is the structured conversation script: introduction, warm-up questions, main body questions organized by topic, probing questions for each, closing questions, and time estimates. The template is what separates rigorous user interviews from open-ended conversations that produce unfalsifiable insights.

The 2026 best practice version of an interview guide has three sections older templates skip: explicit hypotheses the interview is designed to validate or invalidate (so you can recognize the answer when you hear it), leading-question audit (a final check that your questions don't bias toward expected answers), and AI transcription consent language that covers Otter.ai, Fireflies, Granola, and Claude-based summarization that participants need to be informed about under GDPR and similar regulations in 2026.

What makes the User Interviews field guide template the right starting point: it ships with example questions for common research scenarios (new product validation, redesign discovery, churn investigation), which means you do not write every question from scratch.

Where it falls short: interview guides written once and never updated produce stale questions after the first 3-5 interviews. The right practice is updating the guide after each interview based on what worked and what produced thin answers.

4. User persona (2026 format)

Best for: Communicating user insights to stakeholders, aligning teams on who you design for | Tool: Figma, Notion | Source: UXPin's persona examples, Userpilot's 2026 persona guide, UI Prep's free Figma persona template | License: Free download

The single biggest shift in UX research practice between 2022 and 2026 is what goes in a persona. Older templates lead with demographics: age, location, gender, occupation, income, education. Modern personas drop most of that and lead with role, responsibilities, jobs-to-be-done quoted verbatim from interviews, decision criteria, perceived barriers, behavioral signals, and team collaboration map. For B2B SaaS specifically, demographics rarely predict product behavior; role and responsibilities do.

The 2026 persona template structure that works: Name (memorable, role-anchored: "Sarah the Solutions Architect"), Role and team, Responsibilities (3-5 specific job duties), Jobs-to-be-done quoted verbatim from interview transcripts, Decision criteria (what they evaluate vendors on), Perceived barriers (why they would not choose you), Behavioral signals (the product behaviors that prove the persona is in use), Team collaboration (who they hand off to and from), Research source log (which interviews this persona is built from with dates).

What's new in 2026: AI agents as personas. If your product is callable through an API, MCP server, or any agentic interface, AI agents are a measurable share of product usage in 2026. They have jobs to do, success criteria, and failure modes. The persona row for an AI agent includes: model type, task being executed, access pattern, success criteria, failure modes, and what the agent needs from your product (stable APIs, predictable schemas, parseable error messages).

Where most persona templates still fall short in 2026: they read as static posters rather than living documents. The right persona has a "last updated" date, a "based on N interviews" sample size, and a validation cadence (when this persona will be re-checked against real user behavior).

5. Empathy map

Best for: Quick visualization of what one user thinks, feels, says, and does | Tool: Miro, FigJam | Source: Miro's empathy map template, Figma Community empathy map files | License: Free with free account

An empathy map is a four-quadrant visualization (Says, Thinks, Does, Feels) for one user or persona, sometimes with two additional sections (Pains and Gains) added for the "gains and pains" variant. The map is faster to fill out than a full persona and better suited to single-session synthesis after a user interview.

What empathy maps do well that personas don't: capture the emotional and cognitive texture of a specific user in a specific situation. Personas abstract across many users; empathy maps deepen into one. Most teams need both for different purposes.

Where it falls short: empathy maps without source data degenerate into stakeholder assumptions about users dressed up as research. The right empathy map cites specific interview moments ("said in interview #3: 'I just want this to work without thinking'") rather than abstracted summaries.

Evaluative templates: test and validate

6. Usability test script

Best for: Structured usability testing of prototypes or live products | Tool: Notion, Google Docs, Maze | Source: Maze's free usability test templates, User Interviews' usability scripts | License: Free with free account

A usability test script defines the introduction, warm-up tasks, primary task scenarios, success criteria for each task, observation prompts for the moderator, post-task reflection questions, and post-test debrief. The structure is what makes results across 8-12 participants comparable rather than 12 independent conversations.

The 2026 best practice version of a usability test script adds silent observation protocols (when to stay silent and let participants struggle vs when to intervene), think-aloud calibration (how to coach participants to think aloud without contaminating data), and AI moderation considerations if you are using AI tools like Maze AI or UserTesting AI to run unmoderated tests at scale.

What makes Maze's free templates useful: they are pre-formatted for unmoderated testing platforms but adapt cleanly to moderated tests. The structure is identical; only the moderator's job changes.

Where it falls short: usability test scripts written once and used for every test produce stale data after the second study. The right practice is iterating the script after each round based on what surfaced and what was missed.

7. Survey template (Typeform / Google Forms)

Best for: Quantitative validation, gathering data from larger samples | Tool: Typeform free tier, Google Forms | Source: Typeform free template library, Google Forms templates | License: Free tier

Surveys cover the quantitative validation surface that interviews cannot. The right survey complements qualitative research; the wrong survey replaces it and produces vibes-quantified-as-data.

The 2026 survey best practice: keep surveys under 7 minutes (drop-off rates spike past that), use behaviorally anchored scales rather than Likert agreement statements ("In the last 7 days, how many times did you do X?" beats "How often do you do X?" with options "Never / Rarely / Sometimes / Often / Always"), and end with one open-ended question that lets respondents tell you what you forgot to ask.

What makes Google Forms the right starting tool for most research: free, no participant limits, integrates with Google Sheets for analysis, and your participants likely already know the interface. Typeform free tier is the alternative if conversational survey UI matters and you have under 10 responses per month (the free tier limit).

Where it falls short: survey design is a craft. Templates give you the structure; the actual question quality is on you. The single highest-leverage skill in survey design is editing questions ruthlessly to remove leading framings, double-barreled questions, and abstract terms that respondents interpret differently.

Synthesis templates: turn data into insights

8. Affinity diagram

Best for: Pattern-finding across interview transcripts, observation notes, survey responses | Tool: Miro, FigJam | Source: Miro's affinity diagram template, User Interviews' synthesis templates | License: Free with free account

Affinity diagrams cluster raw research notes into themes by moving sticky notes around until patterns emerge. This is the canonical synthesis method for qualitative research; the template is the empty board you fill with your data.

The 2026 affinity diagram practice that matters: use color-coding to track which interview each note came from (so you can see if a theme is one loud participant or actually a pattern), use a separate "outlier" zone for notes that don't fit themes (often the most interesting findings come from these), and time-box clustering to 90 minutes rather than letting it expand to fill available time.

What makes Miro's template useful: real-time collaboration on the same board, infinite canvas (large research projects can have 200+ notes), and Miro AI features in 2026 can suggest cluster patterns based on note content (useful as a starting point, not a substitute for human pattern-finding).

9. Customer journey map

Best for: Visualizing the user's full experience across touchpoints, identifying friction points | Tool: Miro, UXPressia, Smaply | Source: UXPressia free tier templates, Miro Community files | License: Free with free account

A customer journey map visualizes the user's experience across the full lifecycle of a product or service — awareness, consideration, onboarding, daily use, expansion, churn. The map identifies friction points, emotional peaks and valleys, and opportunities for design intervention.

The 2026 best practice adds two layers most older templates miss: AI-touched touchpoints (which steps now involve AI features and how that changes user behavior), and multi-persona overlays (showing where different personas diverge in the journey rather than mapping one journey as if it represents everyone).

What makes UXPressia's free tier useful: pre-built journey map structures that you can customize, with built-in tooling for emotion curves and channel mapping. Miro's free version is the more flexible option if you want to build the structure yourself.

10. Research findings report

Best for: Sharing research outcomes with stakeholders, getting buy-in on recommendations | Tool: Notion, Figma, slide deck | Source: UI Prep's research portfolio templates, User Interviews' presentation templates | License: Free download

A research findings report is the synthesis output most stakeholders will ever see. The template structures findings as: research question, key insights, evidence (quotes and observations), recommendations with priority and effort estimate, and decisions requested.

The 2026 best practice for research reports: structured insights (finding statement → evidence → confidence level → recommended action → owner), decision-readiness framing (each insight points to a specific decision the team needs to make), and executive summary at the top (most stakeholders read only the summary; design it to be the only thing they read).

What separates a research report that drives change from one that gathers digital dust: the recommendations include explicit ownership and timeline. "Recommendation: redesign onboarding to reduce drop-off" gathers dust. "Recommendation: ProductOps owns redesign of onboarding step 3 by Q3, with success measured by drop-off reduction below 15%" gets shipped.

Repository templates: store and reuse insights

11. Research repository (Notion)

Best for: Centralizing research findings, making insights searchable, preventing duplicate research | Tool: Notion | Source: Dovetail-inspired community Notion templates, custom-built | License: Free with Notion free tier (covers individual and small team use)

A research repository is the database where all your team's research lives: study metadata, research questions, findings, participant quotes, recordings, artifacts, recommendations, status. It is the difference between a team that compounds research learnings across quarters and a team that runs the same study every six months because nobody remembers the first one.

The 2026 best practice for a research repository: structured fields (date, researcher, method, participants, key findings, status), tagging taxonomy (theme tags, persona tags, product surface tags), searchable architecture (full-text search across notes), and explicit retention policy (which studies stay forever, which get archived after a year).

What makes Notion the right starting point: it covers 80% of dedicated research repository platforms (Dovetail, Marvin, Condens) at zero cost for individual designers and small teams. Dovetail and Marvin become worth the cost when you have 5+ researchers and 50+ studies; before that, Notion is sufficient. For the broader context on Notion as a designer's tool, see the free Notion templates guide for designers.

12. Research tagging taxonomy

Best for: Making research findings findable six months later | Tool: Notion, Airtable | Source: Custom template (described in this guide) | License: Free

A tagging taxonomy is the rulebook for how research findings get categorized in the repository. Without one, every researcher tags differently, the repository becomes searchable in theory and unusable in practice, and the team rediscovers the same insights every quarter.

The minimum viable taxonomy for 2026: theme tags (5-10 high-level themes specific to your product), persona tags (which personas the finding applies to), surface tags (which product area the finding is about), method tags (interview, survey, usability test, analytics), confidence tags (high/medium/low based on sample size and source quality), decision-state tags (raw insight, validated insight, applied insight, implemented insight).

Where most teams fail: tagging becomes a bureaucracy designers skip because it slows down their work. The right tagging system has 3-5 tags per finding maximum and uses a controlled vocabulary (pre-defined tag list) rather than free-form tagging that drifts over time.

**Browse more research and synthesis resources in the Mantlr directory →**

How to actually use these templates in 2026

Decision framework based on what you are doing:

If you are kicking off a research project: start with the UX research plan (template #1) and the competitive audit template (#2). Spend 1-2 days on these before any user contact. The discipline pays for itself in week 3 when stakeholders try to change scope.

If you are running user interviews: use the user interview guide (#3) and capture findings into the affinity diagram template (#8) after each interview while the conversation is fresh. Build the persona template (#4) only after 5-8 interviews; building personas after 2 interviews produces fiction.

If you are running a usability test: use the usability test script (#6) with 5-8 participants per round. Use the affinity diagram (#8) for synthesis. Skip the formal report (#10) unless stakeholders demand it; a 1-page Notion summary often beats a 20-slide deck.

If you are setting up a research repository: start with the Notion repository template (#11) and the tagging taxonomy (#12). Resist the urge to start with Dovetail or Marvin until you have 30+ studies. Smaller teams produce better repositories with simpler tools.

If you are a solo designer with no formal research budget: combine the user interview guide (#3), the 2026 persona template (#4), and the Notion research repo (#11). These three templates cover 80% of what most design work needs from research, even with no dedicated researcher on the team.

The most common research-template mistake in 2026 is using too many templates simultaneously. The right move is starting with 2-3 templates that match your phase and using them until they are habit; expand the template stack only when the existing set is genuinely insufficient.

What changed in 2025-2026 that matters

Three shifts in UX research practice worth understanding because most pre-2025 template lists miss them:

Demographics-first personas became outdated. The 2026 best practice persona leads with role, responsibilities, jobs-to-be-done quoted verbatim, decision criteria, and behavioral signals. For B2B SaaS, demographics rarely predict product behavior and treating them as primary persona attributes signals an outdated research practice.

AI agents joined the persona library. If your product is callable through API, MCP server, or any agentic interface, AI agents are measurable users in 2026 with their own success criteria and failure modes. Modern persona libraries include non-human users alongside human personas.

Persona simulations entered the workflow. Senior UX teams in 2026 use AI tools to layer over real research transcripts so they can "chat" with personas — asking questions the original interviews didn't cover and getting answers grounded in actual participant language rather than generic LLM output. This is different from synthetic users (which generate fake user data from no real research) and is significantly more useful.

Frequently asked questions

What are the best free UX research templates in 2026?

The most-used free UX research templates for working designers in 2026 are Miro's UX Research Plan template, User Interviews' field guide templates (interview guides, usability scripts), UI Prep's 2026-format persona Figma file, Miro's empathy map and affinity diagram templates, and Notion-based research repository templates inspired by Dovetail's structure. These templates cover discovery through repository stages of the research process and are all free with the parent tool's free tier.

How are 2026 personas different from older persona templates?

The major shift is structural. Older personas lead with demographics (age, location, gender, occupation, income). 2026 personas lead with role, responsibilities, jobs-to-be-done quoted verbatim from interviews, decision criteria, perceived barriers, behavioral signals, and team collaboration maps. For B2B SaaS, demographics rarely predict product behavior; what predicts behavior is what role someone plays, what they are responsible for, and what jobs they are hiring your product to do. Templates that still lead with demographics signal outdated research practice.

Do I need a research repository if I'm a solo designer?

Yes, even at solo scale. A research repository for a solo designer can be a single Notion database with study entries (date, method, participants, findings, decisions made). The discipline is the value, not the tool. Solo designers who keep a research repo compound learnings across projects; solo designers who don't repeat the same discoveries every six months. The Notion repository template described in this guide covers solo and small-team use at zero cost.

What is the difference between an empathy map and a user persona?

An empathy map is a quick four-quadrant visualization (Says, Thinks, Does, Feels) for one user in one situation, useful for capturing the emotional and cognitive texture of a specific interview. A user persona is a structured representation of patterns across many users, abstracted into a research-based archetype. Empathy maps are session-scale tools (one user, one moment). Personas are program-scale tools (the patterns across all your research). Most teams need both for different purposes.

Can I use AI tools to generate personas?

Yes for hypothesis generation when you have zero research data, no. For persona research itself, the 2026 best practice strongly favors personas built from real user interview data with real research source logs. Synthetic users (AI-generated personas with no real research underneath) have been documented to give overly favorable, prioritization-blind feedback and lead to bad product decisions. AI tools are useful for persona simulations layered over real research transcripts (so you can "chat" with the persona using their actual words from interviews) but dangerous as a substitute for actual user research.

What is the best free customer journey map template?

UXPressia's free tier ships pre-built journey map structures with built-in emotion curves and channel mapping, which makes it the most polished free option for designers new to journey mapping. Miro's Community templates are the more flexible choice if you want to customize the structure yourself. For 2026 work, the journey map template should include AI-touched touchpoints (which steps now involve AI features) and multi-persona overlays (showing where different personas diverge in the journey rather than mapping one universal journey).

How long should a user interview guide be?

A user interview guide for a 45-60 minute session typically runs 1-2 pages: 1-2 warm-up questions, 8-12 main body questions organized by topic with probing questions for each, 1-2 closing questions, and time estimates per section. Longer guides (3+ pages, 20+ main questions) signal the researcher hasn't decided what they actually want to learn. The right discipline is editing the guide ruthlessly before fieldwork to remove every question that doesn't directly serve the research objectives.

Where do I store UX research findings in 2026?

For solo designers and small teams (1-5 designers), Notion is sufficient at zero cost. Build a research repository database with structured fields and a tagging taxonomy. For medium teams (5-20 designers, 50+ studies), dedicated research repository tools like Dovetail ($25-50/user/month) or Marvin become worth the cost. For larger teams, the tool choice matters less than the repository discipline: structured tagging, controlled vocabulary, decision-state tracking, and explicit retention policies are what make repositories useful long-term.

Where to go from here

Pick two templates from the list above and apply them to a project this week. Most designers research templates for hours and never actually use one. The discovery (UX research plan + competitive audit) and the synthesis (affinity diagram + journey map) phases are the highest-leverage starting points because most teams skip them entirely and lose 30-50% of research value as a result.

If you have to pick exactly one template to adopt, pick the research repository (#11). The compounding value of structured findings across quarters is the single biggest research practice difference between teams that ship the same insights repeatedly and teams that build product intelligence over years.

Discovering more design resources on Mantlr

Mantlr curates every UX research template, design tool, and resource worth knowing:

**UX Research Resources on Mantlr**: every free UX research template reviewed by the Mantlr team, sortable by phase and tool.
**Free Design System Resources Every Team Needs in 2026**: the broader systems context where research feeds into design tokens and component decisions.
**How to Build a Design Portfolio with Free Resources Only in 2026**: the case study structure that turns research output into portfolio-ready work.
**Free Figma Plugins That Replace Paid Tools in 2026**: the plugin stack including Spelll, Autoflow, and Content Reel that pairs with the research templates.

Good research compounds. Bad research repeats. Mantlr curates 500+ design resources — UX templates, design tools, UI kits, and systems — so you spend time doing the research, not searching for the templates.

Browse the Mantlr Directory →

Sources and methodology

Research conducted May 2026. Template selections cross-referenced against User Interviews' "105 Free UX Research Templates" (userinterviews.com/blog/105-free-uxr-templates-tools-you-already-use, April 2026), User Interviews' "54 Templates for User Personas, JTBD & Other Mental Models" (userinterviews.com, February 2025), Great Question's "40+ Free UX Research Templates" (greatquestion.co/templates, retrieved May 2026), and Miro's UX Research Plan template (miro.com/templates/ux-research-plan, retrieved May 2026). 2026 persona format details from Userpilot's "11 User Persona Examples and Templates" (userpilot.com/blog/user-persona-examples, May 2026), UXPin's "UX Persona Examples: 4 Ready-to-Use Templates for UI Design 2026" (uxpin.com/studio/blog/persona-examples, May 2026), and AND Academy's "7 Free User Persona Templates for UX Designers" (andacademy.com, February 2026). AI agent persona and persona simulation context from Userpilot's coverage of Noz Urbina's persona simulation framework. AI prompts for UX research practice from SurePrompts' "35 AI Prompts for UX Designers" (sureprompts.com, March 2026). User interview template details from Xtensio's free user interview template (xtensio.com/user-interview-template, retrieved May 2026). Research repository structure informed by Dovetail's research repository documentation and 2026 community-built Notion templates.

About Mantlr

Mantlr is a hand-picked directory of design tools, UI kits, templates, and resources for working designers and developers. Every resource is reviewed before listing. We publish weekly guides on the tools designers actually use to ship.

Browse the full Mantlr directory →

Free UX Research Templates Every Designer Should Have in 2026