The difference between ServiceNow Studio and Studio

[SotaT]

I would like to know the difference between ServiceNow Studio and Studio.
Could you please tell us about the following points?
Features of ServiceNow Studio
- Comparison with Studio
- What it can do
- What it can't do
- Where ServiceNowStudio stands (developer rank, who it is for)

[rohansargar]

Hello @SotaT 

What is ServiceNow Studio?
ServiceNow Studio is the integrated development environment (IDE) inside the ServiceNow platform, primarily used to develop classic custom applications. It offers tools to work with:

Script Includes
UI Policies / UI Scripts
Client Scripts
Business Rules
Tables & Fields
ACLs (Access Control Rules)
Workflows (legacy)
Application Files

What is Studio (outside of ServiceNow)?
If you mean "Visual Studio" or other general-purpose IDEs, they are not directly comparable because they are platform-agnostic development tools used for traditional programming (JavaScript, Python, C#, etc.) across many platforms, including frontend/backend apps, mobile apps, and more.

What ServiceNow Studio can do

Full application lifecycle development
Server-side scripting (Business Rules, Script Includes)
Client-side scripting (Client Scripts, UI Scripts)
Code-level access to all platform components
Create and manage Scoped Applications
Integrate with Git repositories
Manage ACLs and security deeply

What ServiceNow Studio can't do

No drag-and-drop UI layout (like UI Builder)
Not designed for low-code developers or business users
Doesn’t support building Workspaces/Experiences (use UI Builder for that)
Doesn’t support flow-based table creation or Guided App Creation

Where does ServiceNow Studio stand in Developer Skill Level?

Studio is best for: Admins, Advanced Developers, ServiceNow Architects
Not for: Business users or Citizen developers

Mark helpful if you got answer for you questions 

Best regards,

Rohan,

[SotaT]

Thank you very much for your answer!
I would like to know how it differs from Legacy Studio. What are some of the differences between legacy Studio and legacy Studio?
As far as we know now,
・You can now do
・Multiple application scopes can be handled by tabs
・You can now switch between update sets within Studio.

　Things that can no longer be done:
・Don't know...

[rohansargar]

Hello @SotaT 

You can now do (New Features in Modern Studio):
Open and work on multiple application scopes using tabs.
Switch between update sets directly from within Studio.
Access an improved file tree navigation with better categorization.
Benefit from faster performance and better UI responsiveness.
Work in multiple tabs for different files (like Script Includes, UI Policies, etc.).
Use a more modern look-and-feel with improved developer experience.
Have a clearer separation between client-side and server-side scripts.
Get better Git integration (especially in newer versions like Utah and Vancouver).

❌ Things that can no longer be done (Limitations in Modern Studio):
You can’t edit form layouts (Form Designer) directly within Studio anymore — it redirects you to the main UI.
You cannot manage global apps easily; Studio is scoped-app focused.
Studio no longer supports managing Flow Designer or UI Builder elements directly inside the interface.
You cannot manage low-code visual components like App Engine Studio provides.
Direct script testing tools (like script execution or test buttons) are more limited than they were in older versions.
Some platform records and system definitions (like ACLs or certain Dictionary fields) are harder or not possible to access from Studio now.

Why is ServiceNow Studio not suitable for Citizen Developers?
Because ServiceNow Studio is a code-heavy, developer-centric IDE, not a guided or visual environment. 

Regards,

Rohan

[SotaT]

@rohansargar 

I just tried and was able to change the form layout in the form designer within STUDIO, has this changed since YOKOHAMA?