Help center · Comparison

FAQ page vs knowledge base: which do you need?

A FAQ is one page of short answers. A knowledge base is a set of separate articles people can search and browse. Neither one is automatically better. It depends on the questions you get.

The difference at a glance

When a FAQ does the job

Say you're launching a small paid app. People ask about the price, refunds, and whether it works on mobile. Put those answers on one page, close to the pricing or signup button. They can read the whole thing in a minute. That's a good FAQ.

FAQs work well for a handful of short questions, especially before someone signs up. They get hard to use when every answer needs five steps, or the page keeps getting longer. Not sure which questions to include? Here are 30 to start from.

When articles make more sense

Now someone needs to connect their account, change notification settings, or fix a failed import. Each task deserves its own link. An article can include steps, context, and a note about what to do if something goes wrong. Group several articles under a clear category and you have the start of a knowledge base.

The biggest practical difference is sharing: “Here's how to retry your import” is more helpful than “Scroll halfway down our FAQ.” Separate pages also let a person arrive straight from a search result.

Signs you've outgrown your FAQ

• The page needs its own table of contents.
• Answers have numbered steps or screenshots.
• You reply to customers with “scroll down to the question about…”
• People still write in about things the FAQ covers. They didn't find them.

Turning a FAQ into a knowledge base

Don't start over. Take the longest answers and give each one its own article, with the question as the title. Leave a one-line answer in the FAQ and link to the article. Group the new articles under a few categories, like Getting started, Billing and Troubleshooting.

Over a few weeks, the FAQ shrinks back to quick pre-sale questions, and the knowledge base grows from real needs.

Can you have both?

Yes. Keep a small public FAQ for pre-sale questions and use a help center for product tasks. You can link between them. Don't paste the same full answer in both places: two copies become two things to keep current.

If you only have a few users, don't invent a large structure. Start with the questions you actually hear. As the product grows, turn long FAQ answers into separate articles and link to them from the FAQ.

And where does a help center fit?

A help center is the page that holds your knowledge base, plus ways to reach you when the articles don't help. Help center vs knowledge base explains it in more detail.

Do you need knowledge base software?

A FAQ needs nothing special: a page on your site, or an accordion block in your site builder. A knowledge base is worth a tool once you have more than a handful of articles. You'll want search, categories, a link for every article and an easy editor. A new product doesn't need a big help desk system for that. Pick something you'll actually keep up to date.

MvpKit's public help pages support individual articles, categories and search, with a contact form on the same page. A separate FAQ isn't required, but you can write a short “Common questions” article if that's the simplest place to start.