# Tips on speeding up NLP? **URL:** \ **Category:** Troubleshooting and Bugs\ **Created:** [July 2, 2025, 4:50pm UTC](https://forums.negativelabpro.com/t/tips-on-speeding-up-nlp/9501 "2025-07-02T16:50:55Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![hubbubjub](https://avatars.discourse-cdn.com/v4/letter/h/3ec8ea/32.png) [@hubbubjub](https://forums.negativelabpro.com/u/hubbubjub)\ **Post date:** [July 2, 2025, 4:50pm UTC](https://forums.negativelabpro.com/t/tips-on-speeding-up-nlp/9501/1 "2025-07-02T16:50:55Z")
I’m running NLP v3.1.1 on a fairly beefy PC (i5-13400, RTX 4070, 16GB RAM) and every change to edit settings on a negative takes 1-3 seconds to reflect on-screen. This is in contrast to the native Lightroom develop experience, where changes happen instantaneously. Do others have this experience? Anything I can do to speed up NLP? ---
**Author:** ![nate](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.negativelabpro.com/nate/32/4_2.png) [@nate](https://forums.negativelabpro.com/u/nate)\ **Post date:** [July 2, 2025, 5:15pm UTC](https://forums.negativelabpro.com/t/tips-on-speeding-up-nlp/9501/2 "2025-07-02T17:15:33Z")
Hi, The tips here in the guide should help! > **[Lightroom Tips | Negative Lab Pro](https://www.negativelabpro.com/guide/lightroom/#speeding-up-lightroom)** > > Part of NLP's power comes from its close integration to Lightroom. Learn how to take full advantage of this integration. The biggest tip is to run NLP from the “Develop” module rather than the Library module. It will make a BIG difference in speed of render. Nate ---
**Author:** ![hubbubjub](https://avatars.discourse-cdn.com/v4/letter/h/3ec8ea/32.png) [@hubbubjub](https://forums.negativelabpro.com/u/hubbubjub)\ **Post date:** [July 2, 2025, 5:24pm UTC](https://forums.negativelabpro.com/t/tips-on-speeding-up-nlp/9501/3 "2025-07-02T17:24:19Z")
Wow okay, I thought NLP got way slower but it must have been that I was previously in the Develop module and now was in the Library module. Thanks! ---
**Author:** ![Digitizer](https://avatars.discourse-cdn.com/v4/letter/d/57b2e6/32.png) [@Digitizer](https://forums.negativelabpro.com/u/Digitizer)\ **Post date:** [July 4, 2025, 10:48am UTC](https://forums.negativelabpro.com/t/tips-on-speeding-up-nlp/9501/4 "2025-07-04T10:48:42Z")
> [@nate](#): > > run NLP from the “Develop” module rather than the Library module. It will make a BIG difference in speed of render. I found that converting the same 138 negatives with the same settings took - 106 seconds in Library - 128 seconds in Develop I’m not saying that the manual is wrong, but differences seem to depend on other things like hardware, OS etc. I was testing on a 2019 5k iMac with physical copies of .CR2 and .CR3 files and converting in Library was quicker from pressing “concert 138 images” to the moment when NLP presents the “Apply” button. Software: LrC 13.4 on macOS 14.7.6 Retesting again, I found that converting in Develop can be as low as measured in Library above. In between tests, I removed images from Lightroom, had it optimise the catalog and synchronised the folder to import the images again. Whatever caused the changes in conversion times wasn’t important enough to turn times clearly in favour of converting in Develop. NLP is fast enough for how I work (10-15 images at one time) and I prefer to convert in Library. For bigger batches, I start the conversion and do something else 😉 ---
**Author:** ![hubbubjub](https://avatars.discourse-cdn.com/v4/letter/h/3ec8ea/32.png) [@hubbubjub](https://forums.negativelabpro.com/u/hubbubjub)\ **Post date:** [July 4, 2025, 6:10pm UTC](https://forums.negativelabpro.com/t/tips-on-speeding-up-nlp/9501/5 "2025-07-04T18:10:37Z")
Interesting data! For me, the bottleneck was adjusting the image, not converting negatives, and moving to Develop for adjustments was night and day. ---
**Author:** ![nate](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.negativelabpro.com/nate/32/4_2.png) [@nate](https://forums.negativelabpro.com/u/nate)\ **Post date:** [July 6, 2025, 3:53pm UTC](https://forums.negativelabpro.com/t/tips-on-speeding-up-nlp/9501/6 "2025-07-06T15:53:48Z")
> [@hubbubjub](#): > > the bottleneck was adjusting the image, not converting negatives, and moving to Develop for adjustments was night and day. Yes, this is what I mean. Making adjustments and edits to a selected image will render in almost real time when in the Develop module, while it is very very slow in the Library module.