WordPress Parse Error Syntax Error Unexpected
What Is This Error?
The WordPress Parse Error (Syntax Error, Unexpected) is a PHP error that completely locks you out of your website. Instead of your normal site, you see a white screen or a plain error message like: Parse error: syntax error, unexpected ‘}’ in /wp-content/themes/yourtheme/functions.php on line 42. This is PHP’s way of saying it found something in your code that it simply cannot make sense of.
The most important detail in that message is the file path and line number. PHP is telling you exactly where it got confused. That said, the actual mistake often lives one or two lines above the reported line — PHP doesn’t realize something is wrong until it hits the next unexpected character downstream.
The good news: this error is almost always caused by a simple typo or a bad copy-paste, which means it’s fixable in minutes once you know where to look.
Get free WordPress & AI tips
Join 500+ readers. No spam, unsubscribe anytime.
Why Does This Happen?
- Manual editing of PHP files: The most common trigger — editing functions.php or a plugin file directly and accidentally deleting a semicolon, a bracket, or a quote character.
- Pasting code with smart quotes: Copying snippets from a blog post or Word document can silently swap straight quotes with curly/smart quotes (“ ”), which PHP cannot parse.
- Incomplete code snippets: Pasting a snippet that’s missing its closing bracket
}or semicolon;breaks the entire file from that point downward. - PHP version mismatch: Code written for PHP 8.x may use syntax that an older PHP 7.x server doesn’t support, triggering a parse error on code that looks perfectly valid.
- Corrupted plugin or theme update: A failed or interrupted update can leave a PHP file written only halfway to disk, producing garbled content PHP can’t execute.
How to Fix It — Step by Step
-
Read the full error message and write down the file path and line number. For example:
Parse error: syntax error, unexpected '}' in /public_html/wp-content/themes/mytheme/functions.php on line 58. These two details are everything.You should see: A file path starting with
/wp-content/and a specific line number in the error output. -
Connect to your server via FTP or open cPanel File Manager. Use an FTP client like FileZilla, or log into your hosting control panel and navigate to File Manager. Go to the exact path shown in the error. Do not attempt to fix this through the WordPress admin — your dashboard is likely inaccessible.
You should see: The directory containing the broken file, accessible through your FTP client or File Manager.
-
Download a backup copy of the broken file before touching it. Right-click the file and save it to your desktop. This is your safety net in case your edit makes things worse.
You should see: The file saved locally on your machine before any changes are made.
-
Open the file in a code editor and jump to the reported line number. Use VS Code, Notepad++, or any plain text editor — never Microsoft Word. Inspect the reported line and the two or three lines directly above it.
# Common issues to look for near the reported line: # - Missing semicolon at the end of a statement # - Unclosed string (missing closing " or ') # - Extra or missing curly bracket { } # - Curly/smart quotes instead of plain straight quotesYou should see: The problematic character near or just above the reported line — visually out of place compared to surrounding code.
-
Fix the syntax error and save the file as plain text. Add the missing semicolon, close the open bracket, or replace curly quotes with straight ones. Save as UTF-8 without BOM.
You should see: No syntax errors flagged by your editor on or around the corrected line.
-
Upload the corrected file back to the server, overwriting the broken version. Use FTP or File Manager to replace the file at the exact same path.
You should see: Your WordPress site loading normally in the browser after a page refresh.
-
If you cannot identify the fix, disable the offending plugin or theme via FTP. Rename the plugin folder to force-deactivate it, or rename your theme folder so WordPress falls back to a default theme.
# Rename via FTP to disable a broken plugin: /wp-content/plugins/broken-plugin → /wp-content/plugins/broken-plugin-DISABLED # Rename via FTP to disable a broken theme: /wp-content/themes/broken-theme → /wp-content/themes/broken-theme-DISABLEDYou should see: Your WordPress site coming back online, running without the disabled plugin or theme.
Common Mistakes When Fixing This
- Editing PHP files through the WordPress Theme/Plugin Editor: If you save a broken file there, you’re locked out instantly with no way to undo from inside WordPress. Always use FTP or File Manager so you can recover the file externally.
- Only checking the exact line number reported: PHP flags where it noticed the problem, not always where the mistake was made. A missing semicolon on line 40 might not surface until line 45 — always scan a few lines above the reported number.
- Opening code in Word or Google Docs: These apps silently convert straight quotes to curly/smart quotes and inject hidden formatting characters. Always use a dedicated code editor like VS Code or Notepad++ for any PHP work.
- Deleting the broken file entirely: Removing functions.php or a required plugin file causes a different — often worse — set of errors. Always fix or restore the file; never just delete it and hope for the best.
Frequently Asked Questions
Will this error delete my posts or pages?
No. A parse error is a code-level problem, not a database problem. Your posts, pages, media, and settings are stored in the WordPress database and are completely untouched by this error. Once you fix the broken PHP file, all your content comes back exactly as it was.
What does “unexpected end of file” mean specifically?
It means PHP reached the end of the file while still waiting for something to close — usually a curly bracket } or a quote. PHP expected more code but the file just stopped. Look for an unclosed function, if block, or loop near the bottom of the file.
The error is pointing to a core WordPress file — did WordPress break itself?
If the path leads into /wp-includes/ or /wp-admin/, the core file was likely corrupted during a failed update. Download a fresh copy of WordPress from wordpress.org (matching your current version), then replace just that one file via FTP. Never overwrite your entire installation without a full backup first.
How do I prevent this error from happening again?
Always test code changes on a staging environment before touching your live site. Use a code editor with PHP syntax highlighting so mistakes get flagged before you save. Set up automatic backups with a plugin like UpdraftPlus so you can roll back in seconds if something ever breaks again.