Is Login One Or Two Words? | The Clear Writing Rule

You’ve seen all three forms: login, log in, and even log-in. Apps mix them. Emails mix them. Some buttons say “Login,” while the help article says “log in,” and your brain goes, “Wait… which one is right?”

The good news: there’s a clean pattern that covers most real writing. Once you learn it, you’ll spot mistakes fast and fix them without second-guessing.

Why This Confusion Keeps Happening

Tech writing borrows everyday words and gives them new jobs. “Log” started as a word tied to records and lists. Then computers arrived, and “log in” became a standard action: you enter credentials to start a session.

After that, the language did what it often does: it shortened. When an action gets used constantly, people turn it into a noun. That’s how we got “a login.” You can see Merriam-Webster treat the noun form as log-in (and related forms) in its dictionary entry for logging on to systems. Merriam-Webster’s “log on” entry shows the noun form alongside the verb usage.

So you’re not seeing random chaos. You’re seeing a word family that grew fast, then got used in different places: buttons, headings, error messages, school portals, bank sites, and work tools.

Login One Word Or Two With A Simple Test

Here’s the test that settles it in seconds:

• If you can put “the” in front of it, use one word: “the login,” “your login,” “a login.”
• If you can put “to” after it as an action, use two words: “log in to the site,” “log in to your account.”

That’s the core idea. You’ll still run into edge cases (hyphens, headings, UI text that copies a button label). We’ll handle those next.

When “Login” Is One Word

Use login as one word when it acts like a thing. In most writing, that means it’s a noun or an adjective.

As a noun (a thing you have or do): “Your login failed.” “I forgot my login.” “The login was blocked after too many attempts.”

As an adjective (describing another noun): “login page,” “login screen,” “login details,” “login link.”

In school or workplace portals, “login” often shows up as a label too: “Login ID,” “Login Name,” “Login Time.” Labels often behave like adjectives, so one word reads clean.

When “Log In” Is Two Words

Use log in as two words when it’s a verb phrase: you’re naming the action.

“Please log in.” “Log in to continue.” “Log in with your email address.” “Try to log in again.”

Try this quick swap: if you can replace it with “sign in,” you’re dealing with a verb phrase. Two words will usually fit.

Where People Slip

Most mistakes come from one of these habits:

• Buttons drive habits: if a site uses “Login” on the button, writers copy it into sentences as a verb.
• Headlines flatten grammar: headings drop helper words, so people default to one form everywhere.
• Spellcheck rarely helps: many editors accept both forms and won’t flag the wrong one in a sentence.

Is Login One Or Two Words? The Rule That Clears It Up

If you want one sentence to keep in your head, make it this:

• “Login” names the access step.
• “Log in” names the act of accessing.

That’s why “login page” (a page) uses one word, while “log in to the page” (an action) uses two words.

Now let’s get practical, because most people aren’t writing grammar examples. You’re writing emails, instructions, essays, resumes, UI text, and maybe code comments.

Common Use Cases And The Best Choice

Use the examples below as patterns you can reuse. If your sentence matches the pattern, the form will usually be right.

In Emails And Messages

Correct: “Please log in to the portal and upload the file.”

Correct: “I can’t access my login right now.”

Wrong pattern to avoid: “Please login to the portal.” (That sentence needs a verb phrase.)

In School Or University Writing

Most academic writing avoids casual tech terms unless you’re writing instructions. If you must use it, keep the grammar clean:

• “Students must log in to the learning platform before starting the quiz.”
• “The login process requires two-step verification.”

In Job Applications And Resumes

This comes up in bullet points and project summaries. Keep it neat:

• “Built a login page with password reset and account lockout.”
• “Implemented ‘log in’ flow with session handling and audit logs.”

In Help Articles And Product Instructions

Many product style guides prefer “sign in” for consistency. Microsoft’s Writing Style Guide, for instance, recommends using “sign in” and avoiding “log in” unless the UI uses that wording. Microsoft’s “sign in, sign out” guidance spells out that preference for their docs.

If you write product instructions, match what users see on-screen. If the button says “Log in,” mirror it in your steps. If the button says “Sign in,” follow that.

Table 1: Forms, Grammar Roles, And When Each Fits

This table is a fast “pick the right form” reference. Use it when you’re editing a draft and want a clean decision without rethinking the whole sentence.

Form	Grammar Role	Best Fit In Writing
login	Noun	When you mean the access step as a thing: “Your login failed.”
login	Adjective	When it labels or describes: “login page,” “login link,” “login details.”
log in	Verb phrase	When you mean the action: “Please log in to continue.”
log in to	Verb phrase + preposition	When you name the target: “log in to your account,” “log in to the portal.”
log-in	Hyphenated noun/adjective (style-based)	Used in some dictionaries and older style systems; common in labels like “log-in screen.”
logon / log-on	Noun/verb (less common)	Seen in older Windows-era writing; keep only if your system uses it.
sign in	Verb phrase	Often preferred in modern UI writing; swap for “log in” when your product uses it.
sign-in	Hyphenated noun/adjective (style-based)	Used in some headlines and labels: “sign-in page,” “sign-in flow.”

Hyphen Or No Hyphen: “Log-in” And Why You Still See It

You’ll spot log-in in dictionaries, older manuals, and plenty of interface labels. The hyphen often appears when writers want to show “this is acting like one unit,” even if it started as a verb phrase.

In most everyday writing, you can treat the hyphen as optional and style-driven:

• If your brand style uses login as the noun/adjective, stay consistent.
• If your style uses log-in as the noun/adjective, stick with it in headings and labels.

Consistency beats mixing. If a page uses “login” in one section and “log-in” in another, it reads like two different editors worked on it.

UI Text Versus Normal Sentences

Here’s a trap that catches writers: UI text and body text follow different rules.

Buttons And Menu Labels

Buttons are short. They often drop grammar to stay compact. A button might read “Login” even though the action in a sentence would be “log in.” That’s fine, as long as your instruction line matches the UI.

Good pairing: “Select Login, then log in with your email.”

That first “Login” is a label (treated like a name). The second is the verb phrase (the action).

Error Messages

Error messages often talk about the noun form: “Login failed.” That reads like “the login attempt failed.” It’s short and familiar.

If you want a fuller, cleaner message, you can use two words: “We couldn’t log in.” That makes the user the subject and keeps it plain.

Editing Checklist That Works In One Pass

When you’re revising a draft, run these quick checks. You can do them in minutes.

1. Scan for “login” used as a verb. If it’s followed by “to” and a target, it probably should be “log in.”
2. Scan for “log in” used as a noun. If it follows “a,” “the,” “your,” it probably should be “login” (or your chosen hyphen style).
3. Match product wording. If the UI says “Sign in,” use “sign in” in steps and keep “log in” out unless you’re quoting a label.
4. Keep headings consistent. Pick one noun/adjective form and stick with it across the page.

Table 2: Quick Picks For Real-World Writing

If you’re writing fast and just need the right phrase that reads natural, use this table as a set of ready-made templates.

Context	Recommended Wording	Notes
Instruction step	“Log in to your account.”	Verb phrase + target reads clean in help text.
Feature label	“Login page”	Adjective form; keep it consistent across headings.
Error message	“Login failed.” / “We couldn’t log in.”	Pick the tone that fits your product voice.
Email to a student	“Please log in to the portal and submit by Friday.”	Clear action line; avoids the common “please login” slip.
Resume bullet	“Built a login flow with reset and lockout.”	Noun use; keep verbs for what you did (“built,” “implemented”).
UI button copy	“Log in” or “Sign in”	Match your design system and keep it steady across screens.

Mini Practice: Fix These In Your Head

Try these fast edits. If you can do them smoothly, the rule has clicked.

• “Please login to view grades.” → “Please log in to view grades.”
• “Your log in is not working.” → “Your login is not working.”
• “Open the log in page.” → “Open the login page.”
• “I can’t remember my login details, so I can’t log in.” → Already fine.

One Style Choice That Keeps Pages Clean

If you publish lots of posts or tutorials, pick a house style and stick to it:

• Option A: Use “log in” for the verb, “login” for the noun/adjective.
• Option B: Use “log in” for the verb, “log-in” for the noun/adjective.

Option A is common in modern web writing. Option B shows up in some dictionaries and older editorial patterns. Either can work if you stay consistent.

If you’re writing product instructions for a specific tool, let the UI decide. If the product says “Sign in,” copy that wording in your steps so the reader can match screen to sentence without friction.

Final Takeaway You Can Trust While Writing Fast

When you’re typing at speed, don’t stall out on this detail. Run the quick test:

• If it’s a thing, write login.
• If it’s an action, write log in.

That single habit fixes most drafts. It also makes your writing look polished in places where readers notice small slips: school instructions, tech tutorials, portal emails, and app copy.