php artisan says it could not open the input file
Could not open input file: artisanShort answer
PHP was asked to run a file called artisan and found nothing at that path. Artisan is a script at the root of every Laravel project, so either the shell is in the wrong folder or the file is missing from the copy you have. Change into the project root, or restore the file.
Fix it fast
1Find out which cause you have
Print the folder you are in and look for the artisan file there.
pwd ls -l artisan2Match what you see, then jump to its fix
What does the error look like?
Could not open input file: artisan
Cause 1 of 2
The shell is in a folder that is not the project root
1Check
PHP opens the script name you give it. The command php artisan means a file called artisan in the current folder, and Laravel keeps it at the application root, not inside app/ or public/.
pwd
ls ..2Fix
Go to the folder that holds artisan, composer.json and the app directory, then run the command.
cd /path/to/my-app
php artisan list3Verify
The command list prints.
php artisan --versionConfirmed by laravel.com
Cause 2 of 2
The artisan file is missing from this copy of the project
1Check
Every Laravel application has an artisan script at its root. If it is absent, the copy is incomplete, for example after a partial upload or a download that lost the file.
ls composer.json app
git status --short artisan 2>/dev/null2Fix
Restore the file from version control. If the project is not under Git, copy artisan from a fresh Laravel project of the same major version.
git checkout -- artisan3Verify
The file exists and runs.
ls -l artisan
php artisan listConfirmed by laravel.com
How do I stop it coming back?
- Open new terminals in the project folder, or use your editor's integrated terminal.
- Keep the artisan file committed and do not exclude it in deployment scripts.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Back end
Composer says the gd extension is missing on a Laravel project
composer install or composer update stops on a package that requires ext-gd
Composer refuses to install a package that requires ext-gd when the PHP binary running Composer has no GD extension.
4 causes, each with a fixBack end
composer require maatwebsite/excel fails to install
Composer says the package needs an older PHP than the one installed
Composer refuses maatwebsite/excel when the PHP version or a PHP extension does not match what the package and PhpSpreadsheet need.
3 causes, each with a fixBack end
composer install says the lock file is not compatible and asks for update
Your lock file does not contain a compatible set of packages. Please run composer update.
composer install checked the locked packages against this machine's PHP and extensions and found a conflict.
3 causes, each with a fixBack end
composer require laravel/horizon fails: ext-pcntl is missing
laravel/horizon v1.1.0 requires ext-pcntl * -> the requested PHP extension pcntl is missing from your system
Horizon needs the pcntl extension, and Composer refuses to install it where PHP lacks that extension.
3 causes, each with a fixBack end
composer require laravel/passport stops with 'requirements could not be resolved'
... but these were not loaded, likely because it conflicts with another require.
Composer found no Passport release that fits your project at once.
4 causes, each with a fixBack end
Composer says the root composer.json requires a PHP version your PHP does not satisfy
Your requirements could not be resolved to an installable set of packages.
Composer compares the php constraint in your composer.json, or in a package, with the PHP that runs Composer.
3 causes, each with a fix