IDE / editor profile
Apache NetBeans for PHP
Short verdict
A practical no-cost bundled IDE for developers who prefer built-in PHP tooling over extension assembly.
Best for
Students, small teams, Apache-license requirements, local PHP projects, and remote FTP/SFTP maintenance.
Not ideal for
Teams needing the deepest framework automation or container-native remote development.
Pricing, license & platforms
| Pricing / model | Free |
|---|---|
| License | Apache License 2.0 |
| Free tier / OSS | Yes (open source) |
| Operating systems | Windows, macOS, Linux |
| Resource use | high |
| Beginner score (1–5) | 4 |
Structured feature support
✓ supported · △ partial/plugin-dependent · ✕ not supported · ? not verified · — n/a. Verified dates live on source metadata.
| Area | Feature | Support | Notes |
|---|---|---|---|
| basics | PHP syntax highlighting | Supported | |
| basics | Integrated terminal | Supported | |
| basics | Beginner friendly | Supported | |
| containers | Docker | Partial / plugin-dependent | |
| containers | Dev Containers | Not supported | |
| containers | WSL | Partial / plugin-dependent | |
| database | Database connections | Supported | |
| database | SQL tools | Supported | |
| debugging | Xdebug | Supported | |
| extensibility | Plugin ecosystem | Supported | |
| extensibility | AI-assisted tooling | Not supported | |
| frameworks | Laravel | Partial / plugin-dependent | |
| frameworks | Symfony | Partial / plugin-dependent | |
| frameworks | WordPress | Partial / plugin-dependent | |
| frameworks | Drupal | Partial / plugin-dependent | |
| frameworks | Magento / Adobe Commerce | Partial / plugin-dependent | |
| frameworks | Laminas / Zend Framework | Partial / plugin-dependent | |
| php | PHP support | Supported | |
| php | Code completion | Supported | |
| php | Inspections and diagnostics | Supported | |
| php | Automated refactoring | Partial / plugin-dependent | |
| php | PHPUnit | Supported | |
| php | Composer | Supported | |
| php | PHPStan | Partial / plugin-dependent | |
| php | Psalm | Partial / plugin-dependent | |
| php | PHP CS Fixer | Partial / plugin-dependent | |
| php | PHP_CodeSniffer | Partial / plugin-dependent | |
| platforms | Windows | Supported | |
| platforms | macOS | Supported | |
| platforms | Linux | Supported | |
| platforms | Browser based | Not supported | |
| pricing | Free to use | Supported | |
| pricing | Commercial option acceptable | Supported | |
| remote | SSH workflows | Partial / plugin-dependent | |
| remote | SFTP | Supported | |
| remote | FTP | Supported | |
| remote | Remote development | Partial / plugin-dependent | |
| resources | Low memory use | Not supported | |
| resources | Large projects | Partial / plugin-dependent | |
| vcs | Git | Supported | |
| vcs | GitHub | Partial / plugin-dependent | |
| vcs | GitLab | Partial / plugin-dependent |
PHP, debugging & toolchain notes
| PHP support | Built-in PHP project support |
|---|---|
| Debugging | Integrated PHP debugger |
| Xdebug | Supported |
| Git | Built-in Git client |
| Docker | Limited compared with container-first editors |
| SSH | Used for SFTP and remote workflows |
| SFTP | Built-in remote project deployment |
| Database tooling | Database explorer and SQL editor |
| Frameworks | Generic PHP support with selected framework integrations |
| Extensions / plugins | Apache NetBeans plugin ecosystem |
Pros
- Free and Apache licensed
- Built-in PHP project support
- Xdebug, Composer, Git, and database tools
- Documented FTP/SFTP workflows
Cons
- Java runtime and moderate-to-high resource use
- Less container-centric than VS Code
- Framework-specific depth varies
Details
Active PHP support in NetBeans 30
Apache NetBeans 30 was released on May 18, 2026, under the project’s regular release schedule. PHP support remains part of the IDE: projects can select an interpreter, language level, source roots, test directories, and run configuration. This is materially different from installing a general editor and then deciding which language server to trust.
The Java-based application is larger than a small text editor, but the bundle gives a coherent interface for code completion, hints, navigation, Composer, PHPUnit, source control, and database work. Current NetBeans itself also has JDK requirements, so deployment documentation should record both the PHP runtime used by the project and the JDK used to run the IDE.
Xdebug and run configurations
NetBeans documents PHP debugging with Xdebug and offers project run configurations for local websites, scripts, and remote websites. Modern Xdebug 3 settings differ from older tutorials that use xdebug.remote_* names and port 9000. Use the current Xdebug documentation for the extension configuration while using NetBeans documentation for IDE-side project behavior.
Path mappings matter when a remote server or container reports filenames different from the local checkout. Verify the PHP SAPI loading Xdebug, confirm the listening port, and use a small entry script before debugging a full request. An IDE can display a session only after Xdebug successfully connects back.
Remote deployment and databases
Official NetBeans tutorials describe FTP and SFTP remote projects, upload-on-save options, synchronization, and importing from a remote server. These are useful for inherited hosting workflows, but synchronization is not a substitute for versioned deployment. Keep credentials outside repositories and move active teams toward Git-based releases where the host allows it.
The database explorer and SQL editor are useful for development schemas. Production access should remain read-limited and governed separately; an integrated database panel does not make ad hoc production changes safe.
Framework expectations
Generic Composer projects work well, while Laravel, Symfony, WordPress, Drupal, Magento, and Laminas depth varies with plugins, annotations, and project conventions. NetBeans can navigate ordinary PHP classes even without framework-specific insight. Treat specialized completion as partial until the exact plugin and framework version are verified.
Selection guidance
Choose NetBeans when a free, open-source, installable IDE with built-in PHP functionality is more appealing than a marketplace stack. Its defaults can be approachable for beginners, especially in classes where everyone uses the same package. Choose a lighter editor for constrained hardware or a commercial PHP IDE when advanced refactoring and framework indexes justify the cost.
Migration notes
Create a PHP project from existing sources, select the real interpreter and language level, then recreate Xdebug and remote run configurations. Review old Zend include paths before carrying them forward.
Setup guides
Related comparisons
Alternatives
- CodeLiteA free cross-platform IDE best known for C/C++, with PHP editing available but limited cu…
- CursorAn AI-first editor based on the VS Code codebase; PHP intelligence remains extension-depe…
- Eclipse PDTAn EPL-licensed PHP IDE built on Eclipse with code assistance, Composer, debugging, and w…
- GeanyA lightweight free editor with basic IDE conveniences and PHP syntax support across deskt…
- GNU EmacsA deeply programmable free editor with PHP modes, LSP clients, terminals, Git tooling, an…
- KateA free KDE text editor with PHP syntax, projects, terminal, Git features, and optional LS…