<p>Instead of </p>

<pre><code>-i "video.av"i
</code></pre>

<p>use</p>

<pre><code>-i "video.avi"
</code></pre>

<p>or simply</p>

<pre><code>-i video.avi
</code></pre>

CC BY-SA 4.0
2019-06-19T20:19:54.160Z
God spot there on the typo :-)
Dr Mayhem
CC BY-SA 4.0
2019-06-18T12:29:51.727Z
2019-06-18T12:29:51.727Z
MarianD
<p>I suspect all these answers are correct, but also watch out for spaces in the filenames and or path.</p>
<p>For example my batch file was failing due to have a space  <code>.../VSCode Workspace/...</code> in my path.</p>

CC BY-SA 4.0
2022-03-09T13:16:49.743Z
2022-03-09T13:16:49.743Z
Alexander
<p>To be fair, this isn't actually anything to do with ffmpeg. You're using Windows cmd incorrectly. When you call up another executable in cmd, you have tell Windows where to find it. One way is by navigating to the correct folder in cmd before you run the commands. That would be the <code>cd</code> command that changes the working folder. The other way is to map the folder in the system paths, so that you can be in any working folder to use the executable.</p>

<p>In addition to your typo fixes, I strongly recommend mapping a system path to your ffmpeg bin. In other words, actually install ffmpeg. This will allow you to run ffmpeg commands from any working folder displayed in cmd. But your commands will still have to point to the correct folders and files. The only reason I wouldn't bother installing ffmpeg as instructed below is if I'm only temporarily using the system to run a few commands. If I know I'm likely to run future ffmpeg commands on that system, I take the extra few minutes to map the system path and install it.</p>

<p>From <a href="https://video.stackexchange.com/a/20496/3643">How do I set up and use ffmpeg in Windows?</a></p>

<blockquote>
  <ol start="4">
  <li>Before you can use <code>ffmpeg.exe</code> in <code>cmd</code> you have to tell your computer where it can find it. You need to add a new system path.
  First, right click This PC (Windows 10) or Computer (Windows 7) then
  click <code>Properties &gt; Advanced System Settings &gt; Advanced tab &gt;
  Environment Variables</code>.  </li>
  <li>In the Environment Variables window, click the "Path" row under the "Variable" column, then click Edit  <a href="https://i.sstatic.net/Ig6nr.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/Ig6nr.jpg" alt="Steps to add a System path to Windows"></a></li>
  <li>The "Edit environment variable" window looks different for Windows 10 and 7. In Windows 10 click New then paste the path to the folder
  that you created earlier where <code>ffmpeg.exe</code> is saved. For this
  example, that is <code>C:\Program Files\ffmpeg\bin\</code>  <a href="https://i.sstatic.net/D1FO8.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/D1FO8.jpg" alt="Add new system path Windows 10]"></a>  In Windows 7 all the variables are listed in
  a single string, separated by a semicolon. Simply go the the end of
  the string, type a semicolon (<code>;</code>), then paste in the path.  <a href="https://i.sstatic.net/Ox5J8.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/Ox5J8.jpg" alt="Add new system path Windows 7"></a></li>
  <li>Click Ok on all the windows we just opened up.</li>
  </ol>
  
  <p>ffmpeg is now "installed". The Command Prompt will now recognize
  ffmpeg commands and will attempt to run them.</p>
</blockquote>

CC BY-SA 4.0
2020-03-19T00:27:16.477Z
what has path got to do with anything. He is able to run ffmpeg
barlop
CC BY-SA 4.0
2020-03-19T00:53:07.790Z
@barlop This answer's not only for the OP, whose error was apparently only a typo. New command line users get a similar message for a different reason that this answer solves.
user3643
CC BY-SA 4.0
2020-03-19T01:23:02.257Z
Just look at the question he asked. The OP's question shows ffmpeg running, you are not answering the question he asked. If you want to answer a different question of A) ffmpeg isn't running and B) They get the different error of "'sdfs' is not recognized as an internal or external command, operable program or batch file."    Then your answer would perhaps apply. Right now your "answer", or the bulk of it, is for a different question and a different error
barlop
CC BY-SA 4.0
2019-06-20T18:45:46.157Z
2019-06-20T18:51:40.263Z
2019-06-20T18:51:40.263Z
user3643
<p>Help I always get this I dont know why<img src="https://i.sstatic.net/n8kBG.png" alt="![Picture of the Problem">]<a href="https://i.sstatic.net/n8kBG.png" rel="nofollow noreferrer">1</a></p>

CC BY-SA 4.0
2019-06-18T19:00:13.453Z
Your file is in `E:\ffmpeg\bin`. So, after opening command prompt. Type `E:` Press <Enter>, then type `cd \ffmpeg\bin`, then use your command.
Gyan
<video>
FFMPEG No such File or Directory Problem
hiper prorer
# FFMPEG No such File or Directory Problem

(Asked by: username_0 on 2019-06-18)

Help I always get this I dont know why![![Picture of the Problem](https://i.sstatic.net/n8kBG.png)][1](https://i.sstatic.net/n8kBG.png)

**Tags:** video

> **Comments:**
> **username_1**: Your file is in `E:\ffmpeg\bin`. So, after opening command prompt. Type `E:` Press <Enter>, then type `cd \ffmpeg\bin`, then use your command.  

---

## 3 answers

### Answer by username_2 on 2019-06-18. Score: 2

Instead of 
-i "video.av"i

use
-i "video.avi"

or simply
-i video.avi

> **Comments:**
> **username_3**: God spot there on the typo :-)  

---

### Answer by username_4 on 2022-03-09. Score: 0

I suspect all these answers are correct, but also watch out for spaces in the filenames and or path.

For example my batch file was failing due to have a space `.../VSCode Workspace/...` in my path.


---

### Answer by username_5 on 2019-06-20. Score: 0

To be fair, this isn't actually anything to do with ffmpeg. You're using Windows cmd incorrectly. When you call up another executable in cmd, you have tell Windows where to find it. One way is by navigating to the correct folder in cmd before you run the commands. That would be the `cd` command that changes the working folder. The other way is to map the folder in the system paths, so that you can be in any working folder to use the executable.

In addition to your typo fixes, I strongly recommend mapping a system path to your ffmpeg bin. In other words, actually install ffmpeg. This will allow you to run ffmpeg commands from any working folder displayed in cmd. But your commands will still have to point to the correct folders and files. The only reason I wouldn't bother installing ffmpeg as instructed below is if I'm only temporarily using the system to run a few commands. If I know I'm likely to run future ffmpeg commands on that system, I take the extra few minutes to map the system path and install it.

From [How do I set up and use ffmpeg in Windows?](https://video.stackexchange.com/a/20496/3643)

> 4. Before you can use `ffmpeg.exe` in `cmd` you have to tell your computer where it can find it. You need to add a new system path.
>    First, right click This PC (Windows 10) or Computer (Windows 7) then
>    click `Properties > Advanced System Settings > Advanced tab >
>    Environment Variables`.
> 5. In the Environment Variables window, click the "Path" row under the "Variable" column, then click Edit [![Steps to add a System path to Windows](https://i.sstatic.net/Ig6nr.jpg)](https://i.sstatic.net/Ig6nr.jpg)
> 6. The "Edit environment variable" window looks different for Windows 10 and 7. In Windows 10 click New then paste the path to the folder
>    that you created earlier where `ffmpeg.exe` is saved. For this
>    example, that is `C:\Program Files\ffmpeg\bin\` [![Add new system path Windows 10]](https://i.sstatic.net/D1FO8.jpg)](https://i.sstatic.net/D1FO8.jpg) In Windows 7 all the variables are listed in
>    a single string, separated by a semicolon. Simply go the the end of
>    the string, type a semicolon (`;`), then paste in the path. [![Add new system path Windows 7](https://i.sstatic.net/Ox5J8.jpg)](https://i.sstatic.net/Ox5J8.jpg)
> 7. Click Ok on all the windows we just opened up.
>
> ffmpeg is now "installed". The Command Prompt will now recognize
> ffmpeg commands and will attempt to run them.

> **Comments:**
> **username_6**: what has path got to do with anything. He is able to run ffmpeg  
> **username_5**: @username_6 This answer's not only for the OP, whose error was apparently only a typo. New command line users get a similar message for a different reason that this answer solves.  
> **username_6**: Just look at the question he asked. The OP's question shows ffmpeg running, you are not answering the question he asked. If you want to answer a different question of A) ffmpeg isn't running and B) They get the different error of "'sdfs' is not recognized as an internal or external command, operable program or batch file."    Then your answer would perhaps apply. Right now your "answer", or the bulk of it, is for a different question and a different error  

---

