FAQ, Faq, FAQs or Faqs— which one should you actually use?
The version you pick — FAQ, FAQs, Faq, or Faqs — affects how professional your content reads at a glance. The choice isn’t arbitrary: style guides are consistent, and two of these forms should simply never appear in published work.
FAQ
All capitals. The standard initialism form. Use for section titles, navigation labels, page headings, and schema markup.
FAQs
Plural form. Correct in running prose when referring to multiple question sets or documents — not for UI labels.
Faq
Mixed case. Reads as a typo or an unfamiliar proper noun. Contradicts every professional style guide in use.
Faqs
Mixed-case plural. Visually awkward — and in certain fonts, can read as something entirely unintended.
FAQ stands for Frequently Asked Questions. As an initialism — where each letter represents a separate word — it follows the same convention as NASA, HTML, or PDF: all capitals, always.
It’s the most recognised form across the web, appearing consistently in navigation menus, help-centre headings, schema markup (FAQPage), and technical documentation. When in doubt, this is the form to use.
Use FAQ when
- Labelling a page, section, or tab
- Adding a navigation or menu item
- Writing a heading inside your content
- Applying schema markup (FAQPage)
Why it works
- Immediately recognisable to readers
- Consistent with initialisations in all style guides
- Reads cleanly in any font weight or size
- No ambiguity about meaning or intent
FAQs is the plural form and is grammatically sound when referring to multiple distinct question sets, or when using the word as a countable noun in running prose. It follows the same pattern as “PDFs,” “URLs,” or “APIs.”
Use FAQs here
- Referring to multiple distinct FAQ documents
- “We maintain FAQs for each product line”
- “Staff answered 200 FAQs this month”
- Discussing FAQs as a content category
Stick with FAQ here
- A section heading or page title
- Navigation links and menu items
- Schema markup (always FAQPage)
- Any UI label or button text
They look like typos
Mixed-case initialisations (“Faq”) read as a misspelled word or unfamiliar proper noun — not the familiar acronym the reader knows. The eye registers it as wrong before the brain processes it.
No style guide endorses them
Not AP, Chicago, Microsoft, Google, nor any other widely used reference documents “Faq” or “Faqs” as a valid form. There is simply no professional precedent for using them.
Visual ambiguity in certain fonts
“Faqs” — depending on font, weight, and letter-spacing — can read as something entirely unintended at a glance. That’s not an impression any help page wants to make.
Signals unreviewed copy
Content using “Faq” suggests the author wasn’t certain, or the text wasn’t proofread. On a documentation or support page, that’s exactly the wrong signal to send.
Every major reference uses FAQ in all capitals and acknowledges FAQs only as a plural noun in running prose. None of them mention “Faq” or “Faqs” — because there’s nothing to say about them.
Microsoft Style Guide
Uses “FAQ” for labels and headings. “FAQs” accepted in body text for plurals.
AP Stylebook
Recommends all-caps for initialisations. No entry for “Faq” or any lowercase variant.
Google Developer Docs
Uses “FAQ” throughout its documentation standards. The word “Faq” does not appear.
Wikipedia
The FAQ article uses all-caps throughout, reinforcing standard usage across web contexts.
Chicago Manual of Style
Initialisations are capitalised. Plurals formed by adding a lowercase “s” — giving “FAQs.”
The Practical Rule
If every letter abbreviates a separate word, it’s all caps. The only allowed exception is a lowercase plural “s.”
Working on a help centre, documentation site, or FAQ section? GeoSaffer covers writing, design, and the practical details that make digital content actually work.
Explore GeoSaffer →