# Hex file generator vs Target directory in Workbench - Any Difference?
**URL:** https://community.particle.io/t/hex-file-generator-vs-target-directory-in-workbench-any-difference/65924
**Category:** Developer Tools
**Created:** [December 2, 2023, 8:14pm UTC](https://community.particle.io/t/hex-file-generator-vs-target-directory-in-workbench-any-difference/65924 "2023-12-02T20:14:51Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@jgskarda](https://community.particle.io/u/jgskarda)
#### Post date: [December 2, 2023, 8:14pm UTC](https://community.particle.io/t/hex-file-generator-vs-target-directory-in-workbench-any-difference/65924/1 "2023-12-02T20:14:51Z")
Is there any difference between these two files:
- Taking a .BIN file from a compiled particle program and using the Hex File Generator too: [Hex File Generator | Tools | Particle](https://docs.particle.io/tools/developer-tools/hex-generator/)
- Hex file that gets generated in VS Code/Workbench during compiling: {Project Name}\target\5.5.0\boron\ {Project name}.hex
Can I use the .HEX file directly in the target directory or do I always have to generate it from a .BIN file using the Hex Generator Tools?
Just seeing if I can eliminate a step in the deploying new firmware process.
---
### Author:  [@rickkas7](https://community.particle.io/u/rickkas7)
#### Post date: [December 2, 2023, 8:50pm UTC](https://community.particle.io/t/hex-file-generator-vs-target-directory-in-workbench-any-difference/65924/2 "2023-12-02T20:50:52Z")
The hex file in target directory only contains the user firmware. The hex generator hex file contains Device OS, bootloader, and other files like nRF52 SoftDevice.
---
### Author:  [@system](https://community.particle.io/u/system)
#### Post date: [June 2, 2024, 8:51am UTC](https://community.particle.io/t/hex-file-generator-vs-target-directory-in-workbench-any-difference/65924/3 "2024-06-02T08:51:47Z")
This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.