# Production Mode vs Development Mode in Kibana

**URL:** <https://discuss.elastic.co/t/production-mode-vs-development-mode-in-kibana/91078>\
**Category:** Kibana\
**Created:** [June 28, 2017, 10:09am UTC](https://discuss.elastic.co/t/production-mode-vs-development-mode-in-kibana/91078 "2017-06-28T10:09:01Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Marius\_Dragomir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_dragomir/32/42087_2.png) [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)\
**Post date:** [June 28, 2017, 12:41pm UTC](https://discuss.elastic.co/t/production-mode-vs-development-mode-in-kibana/91078/2 "2017-06-28T12:41:42Z")

</div>

Hello,  
In order to run kibana in dev mode, you need to specify the `--dev` flag to the Kibana CLI while running it.  
You can tell Kibana is running in dev mode if you have the `kibana.dev.yml` file present.  
There are potential problems when running Kibana in dev mode, as it's noted in the Contributing guide ( [https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md](https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md) ) :

> In development mode, Kibana runs a customized version of Webpack with some optimizations enabled to make building the browser bundles as fast as possible. These optimizations make the build process about 2x as fast for initial builds, and about 7x faster for rebuilds, but are labeled "unsafe" by Webpack because they can sometimes cause changes to go unnoticed by the compiler.

---

_[View the full topic](https://discuss.elastic.co/t/production-mode-vs-development-mode-in-kibana/91078)._