Log In Or Login | Clean Copy That Looks Professional

You’ve seen it a thousand times: a button that says “Login,” a sentence that says “Please login,” and a help article that mixes both in the same paragraph. People still understand you, but the writing looks sloppy—and on a site that teaches, that’s a missed chance to sound sharp.

This article clears it up in plain English, then gives you patterns you can apply to websites, apps, and school portals. You’ll leave with rules you can remember and examples you can copy.

Why This Tiny Choice Changes How Your Writing Feels

When a reader hits a sign-on screen, they’re often tense. They want access, not a grammar puzzle. If your wording is steady, they relax. If your wording flips between forms, they pause and second-guess what you mean.

On learning sites, teachers and students quote your instructions. Small wording choices spread fast, so a clean standard pays off.

Log In Or Login For Ui Copy: The Simple Rule

Rule of thumb: if you can replace the phrase with “sign in,” write it as two words: “log in.” If you can replace it with “account access,” write it as one word: “login.”

That’s the whole game. One is an action (a verb phrase). The other is a thing (a noun) or a describing word (an adjective).

When “Log In” Is The Right Form

Use “log in” when someone does the action.

• Log in to your dashboard.
• If you can’t log in, reset your password.
• You’re logged in on two devices.
• The app keeps logging in and out on its own.

Notice the grammar helpers around it: “to log in,” “can’t log in,” “logged in,” “logging in.” They behave like a verb.

When “Login” Is The Right Form

Use “login” when you mean a thing people have, use, or see.

• Use your login to access the course.
• The login page is down.
• That login button opens a new tab.
• Ask IT for a new login.

Here “login” acts like “password,” “account,” or “portal.” It can sit after “a,” “the,” or “your.”

What About “Log-In” With A Hyphen?

You’ll run into “log-in” used as an adjective: “log-in screen” or “log-in details.” Many teams skip the hyphen and write “login screen” instead. Pick one house style and stick with it across menus, headings, and help pages.

If you already use “sign in” across your product, that choice removes the whole issue. Some editorial teams prefer “sign in” because it feels friendlier in general UI text.

Consistency Beats Perfection In Product Screens

In interface writing, consistency matters more than winning a debate. If your button says “Login,” your instructions can mirror the UI label, even if the label isn’t the form you’d choose in a school essay.

This is not a free pass to be messy. It’s a reminder to match what the user sees. If your app uses “Log in,” keep that exact casing and spacing in the help steps.

Common Places People Get This Wrong

Most mix-ups happen in the same spots. Fix those and your pages start reading clean right away.

Buttons And Menu Items

Many products use “Login” as a button label because it’s short. If your product already uses “Log in,” keep it. If you’re choosing from scratch, pick one pattern and apply it everywhere: header, mobile menu, and modal dialog.

Error Messages And Alerts

Error text needs to be blunt and clear. Use the action form when telling the user what failed.

• We couldn’t log in with that password.
• Try again, or reset your password.

Headings In Help Articles

Headings often become navigation links, so a mismatch stands out. A heading like “Fix Login Issues” pairs well with body text like “If you can’t log in…”. That split is normal: noun in the heading, verb in the sentence.

Forms And Field Labels

A field label can read “Email” and “Password” with a button that reads “Log in.” If you label the whole area, “Login” works: “Login details,” “Login options,” “Login methods.” Keep the page consistent.

Code Comments And Variable Names

Developers often name things login because code style favors single tokens. That doesn’t force your UI text to do the same. Treat code as code, and treat interface copy as copy.

Many style guides lean the same way on the grammar distinction. Google’s documentation guide lists “login” as a noun or adjective and “log in” as the verb form. Google developer documentation style guidance also notes that “sign in” is often preferred for the verb in user-facing text.

Microsoft’s Writing Style Guide goes a step further for its own products: it recommends “sign in” and “sign out” unless the UI uses different wording. Microsoft’s entry on log on and log off explains that preference and when to mirror the UI label.

Choose A House Style In Three Minutes

If you manage a site with multiple writers or older pages, set a house style so edits don’t turn into back-and-forth.

Step 1: Decide Your Primary Ui Verb

Pick one: “log in” or “sign in.” If your UI already says “Sign in,” copy that.

Step 2: Decide The Noun You’ll Use

Pick one noun for the object the user interacts with: “login page,” “login screen,” “login form,” “login link.” Use that noun form in headings, navigation items, and link text.

Step 3: Lock Your Casing

Choose whether your button uses “Log in” based on your UI rules. Then match it across desktop and mobile. A single mismatch makes a page look patched together.

Table: Where Each Form Fits In Real Screens

Context	Best Form	Notes
Button text	Log in / Sign in	Match your product’s chosen verb; keep casing consistent.
Navigation link to the sign-on page	Login (or Sign in)	Noun labels scan fast in menus; mirror the destination page title.
Instruction steps	Log in	Use the action form: “Log in, then open Settings.”
Error message	Log in	Keep it direct: “Can’t log in” reads cleaner than “Can’t login.”
Page title	Login	Common pattern: “Login” or “Login to Your Account.”
Describing a screen element	Login (adjective)	“Login button,” “login form,” “login modal.”
Past tense status	Logged in	Two words. Treat it like “signed in.”
Ongoing status	Logging in	Two words. Handy for loading states: “Logging in…”
Headings in help content	Login (heading) + log in (body)	Mixing is fine when grammar matches the sentence role.

Write Instructions That Users Can Follow Without Re-Reading

Grammar rules are only useful when the steps work on the first try. When you write help text for a school portal, a course platform, or a learning app, keep the flow tight.

Use The Same Words As The Screen

If the button says “Log in,” your step should say “Select Log in.” If the menu says “Login,” your step should say “Select Login.” This reduces mistakes when users scan quickly.

Say What The User Should Do Next

Try a two-beat rhythm: action, then result.

• Log in, then open your profile.
• Log in, then pick your class from the list.
• Log in, then check your inbox for the code.

Those sentences stay clear even when translated or shortened for mobile screens.

Seo And Accessibility Notes For Login Wording

On learning sites, “login” is often what people type into search boxes, even when the action form is “log in.” A simple pattern works well: noun form in page titles and headings, verb form in steps.

For accessibility, keep link text specific when you have more than one entry point, like “Student login” and “Teacher login.”

Common Variations: Log In, Sign In, Log On, And More

You’ll meet related pairs that follow the same pattern:

• Sign in (verb) vs sign-in or signin (noun/adjective in some brands)
• Log out (verb) vs logout (noun/adjective)
• Set up (verb) vs setup (noun/adjective)

“Log on” shows up in older systems and enterprise software. If your UI says “Log on,” follow the UI. If you’re writing general education content, “log in” and “sign in” are the forms most learners meet first.

Table: A Quick Editing Checklist For Teams

Check	What To Look For	Fix
Verb vs noun	“Please login” in sentences	Change to “Please log in” or drop “Please.”
Headings	Mixed casing: “login,” “Login,” “LOG IN”	Match your site’s heading case rules.
Buttons	Menu says “Login,” button says “Log in”	Pick one label pattern and update all instances.
Error text	“Login failed” used as a sentence	Use “Log in failed” or “We couldn’t log in.”
Status text	“You are login” or “You are logined”	Use “You’re logged in.”
Links	Several links all labeled “Login”	Make them specific: “Student login,” “Admin login.”
Microcopy near fields	“Enter login” without context	Say “Enter your email” or “Enter your username.”
Translations	Two terms translated to one word	Keep the UI term steady; clarify in help text if needed.

Copy-Paste Examples You Can Use Right Away

If you’re writing for a school or course site, these patterns keep your text clean and familiar. Swap the nouns to fit your platform.

For Buttons And Links

• Log in
• Student login
• Teacher login
• Log out

For Step-By-Step Help

• Open the portal, then log in with your email and password.
• If you can’t log in, select “Forgot password” and follow the prompts.
• After you log in, open “Courses” to see your enrolled classes.
• If you’re logged in on a shared device, log out when you’re done.

For Troubleshooting Lines

• The login page isn’t loading: refresh, then try again.
• You changed your password but can’t log in: wait a minute, then retry.

How To Teach This To Learners Without Overloading Them

For English learners, keep it short: “Two words for the action, one word for the thing.” Then show three paired examples and stop there. Practice sticks when students spot it on real screens.

One Last Pass Before You Publish

Run a quick site search for “ login ” and “ log in ” with spaces around the phrase. Spot-check the top templates: header, footer, and the main sign-on screen. Then scan the help articles that mention access issues.

After that, you’re done. Your writing will look cleaner, your instructions will read smoother, and your learners will spend less time stuck at the door.