We just raised a $30M Series A: Read our story

SharePoint Designer OverviewUNIXBusinessApplication

SharePoint Designer is #3 ranked solution in top .NET Development Services. IT Central Station users give SharePoint Designer an average rating of 8 out of 10. SharePoint Designer is most commonly compared to Microsoft Visual Studio:SharePoint Designer vs Microsoft Visual Studio. The top industry researching this solution are professionals from a computer software company, accounting for 26% of all views.
What is SharePoint Designer?
SharePoint Designer is the tool of choice for the rapid development of SharePoint applications. Using SharePoint Designer, advanced users and developers alike can rapidly create SharePoint solutions in response to business needs. Advanced users can compose no-code solutions that encompass a variety of common scenarios, from collaborative sites and web publishing to Line-Of-Business data integration, business intelligence solutions, and human workflows, leveraging the building blocks available in SharePoint in an easy to use environment.
SharePoint Designer Buyer's Guide

Download the SharePoint Designer Buyer's Guide including reviews and more. Updated: November 2021

SharePoint Designer Customers
Pyrotek Inc., ICA, Deliver Australia, Secretary of Economy of Mexico, Aegon, ABB Switzerland, Ascent Yarns Private Limited, Bakewell Biscuits Pvt Ltd, Hitachi Consulting
SharePoint Designer Video

Archived SharePoint Designer Reviews (more than two years old)

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Manish_Kumar
Solution Architect at Al
Real User
Offers data mining, exploring and editing content features but is somewhat outdated

Pros and Cons

  • "We used SharePoint Designer 2013 widely for data mining, exploring the content, and editing. Those are the main features that you would need to use SharePoint Designer for."
  • "SharePoint Designer is not releasing a new version. Version 2013 was the latest version. Now in 2019, we are still using the biggest version. It doesn't work properly anymore. Sometimes we experience issues, but there is no new version."

What is most valuable?

We actually don't use Designer much in the latest version of SharePoint, since we can use any other designer in the new SharePoint architecture. Previously, however, we used SharePoint Designer 2013 widely for data mining, exploring the content, and editing. Those are the main features that you would need to use SharePoint Designer for.

What needs improvement?

SharePoint Designer is not releasing a new version. Version 2013 was the latest version. Now in 2019, we are still using the biggest version. It doesn't work properly anymore. Sometimes we experience issues, but there is no new version. 

There are many things that could be improved in SharePoint Designer. The user interface definitely is a very old design, but as a developer, I would concentrate more on the functionality. With the newer interfaces, just basic functionality is provided to explore the content. The editing method should be changed, as inline editing is not recommended. Now we create apps, which can change the user interface and the functionality as well.

There are some features that need to be worked out with the current version. There are several issues, but I can't think of them right now. There are lots of things that we to in newer versions. We use other tools for that, but that functionality was not possible with SharePoint Designer.

For how long have I used the solution?

I've been using this solution for almost ten years.

What do I think about the stability of the solution?

Some functionality is missing in the newer version, but in the previous version, it was good.

How was the initial setup?

The initial setup was straightforward.

What other advice do I have?

I've been working with SharePoint version 2013. I would rate it as 7.5 out of ten.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
JB
Owner with 51-200 employees
Real User
A solution with poor UX/UI, lots of bugs and difficult management functionality

Pros and Cons

  • "The basic functionality the solution makes it easy to share documents or information with the team."
  • "It has a lot of bugs. It's also not very convenient. The UX/UI is not very user-friendly and not designed to be similar to other applications from Microsoft."

What is most valuable?

The basic functionality the solution makes it easy to share documents or information with the team. 

What needs improvement?

SharePoint is not a great product. It can be much better in many ways. 

The collaboration tools for editing do not work right and malfunction often.

It has a lot of bugs. It's also not very convenient. The UX/UI is not very user-friendly and not designed to be similar to other applications from Microsoft. 

The management functionality should be much easier. 

The dialogue with end users needs improvement. If you are a manager of SharePoint, sometimes it's hard to know what exactly the user would like to have. There should be more intelligent services or features available, which would make it easier for end users. 

For how long have I used the solution?

I've been using the solution for seven years.

What do I think about the stability of the solution?

There are many bugs in the solution, so I don't think it's extremely stable.

What do I think about the scalability of the solution?

Although I'm not in charge of scaling the solution, I've heard it's not very easy to expand the capacity.

How are customer service and technical support?

I've never contacted Microsoft directly, as our enterprise has its own internal support.

How was the initial setup?

I didn't do the initial implementation, but I set up the team functionality, and that part of the setup was not easy.

What other advice do I have?

We use the on-premises deployment model.

I'd rate the solution three out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Find out what your peers are saying about Microsoft Visual Studio vs. SharePoint Designer and other solutions. Updated: November 2021.
554,529 professionals have used our research since 2012.
MichaelSoliman
Owner at Alopex ONE UG
Real User
Easy to install and allows direct access to data structures

Pros and Cons

  • "The most valuable feature is the capability to directly access the SharePoint data structure."
  • "It would be helpful to have the SharePoint Designer capabilities built directly into SharePoint itself, into the management page, so as to create an online version of it directly in SharePoint."

What is our primary use case?

My primary uses for this solution are attaching workflows and customizing pages.

Our deployment is mostly on-premises.

What is most valuable?

The most valuable feature is the capability to directly access the SharePoint data structure. It is a tool that is similar to a registry editor, but specific to SharePoint.

What needs improvement?

I would like to see the complete mapping of our data types, including previews, which were switched off at some point.

It would be helpful to have the SharePoint Designer capabilities built directly into SharePoint itself, into the management page, so as to create an online version of it directly in SharePoint.

For how long have I used the solution?

Including FrontPage, I have been using this solution for sixteen years.

What do I think about the stability of the solution?

There have been issues at times, but in general, it is stable.

What do I think about the scalability of the solution?

This is a problem that does not occur at all. SharePoint Designer puts its configuration data into a firm structure, which is parallelized by default and thread protected. It does not matter which means you use in to access the data, whether it is through direct API calls or in SharePoint Designer. It is protected against all structures within the form. You cannot override data. It is inherently parallelized by SharePoint, itself.

There are approximately ten users working within our support company, but the company using this solution has about five hundred end-users.

How are customer service and technical support?

I have contacted technical support in the past, and it took a few hours, but Microsoft called back and solved the problems. I found them to be pretty fast.

Which solution did I use previously and why did I switch?

Prior to this solution, I was using PowerShell to perform the same tasks.

How was the initial setup?

The initial setup of this solution is easy. There are just a few clicks, you enter the path and the licensing information, and then continue to click Next until it is finished. It is not like Oracle, where you have to know fifty parameters before installing.

What other advice do I have?

This solution started as Microsoft FrontPage and was renamed at some time.

My advice for anybody who is implementing this tool is to make sure that you understand it. This tool can damage a lot if you don't know what you are doing. If you are only editing your own sites then there is not much damage you can do. However, if you have elevated access then you have to be careful. It is similar in this regard to a registry editor, where if you edit keys outside of your own personal scope then it can cause problems. You can do a lot of damage to your machine.

The biggest lesson that I learned when using this solution has to do with planning. When it comes to using this solution, it is much better to plan what you are doing in advance. Just clicking around trying to get things done is inefficient, and you will spend a lot more time than necessary.

I would rate this solution a nine out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
RA
Corporate Website Manager, Manager of Technical Documentation at a manufacturing company with 1,001-5,000 employees
Real User
A solution with great workflow and good stability but it needs more web-based publishing

Pros and Cons

  • "The workflow is the solution's most valuable feature."
  • "The solution requires more web-based publishing. It would benefit from adding in more collaboration features as well."

What is our primary use case?

We primarily use the solution as our internet and extranet platform and for our software.

What is most valuable?

The workflow is the solution's most valuable feature.

What needs improvement?

We work mostly with documentation and we'd like to have  it be more of a web-based. Right now, our product, our system is only set up for PDF and we're looking for a better web-based solution for our documentation.

The solution requires more web-based publishing. It would benefit from adding in more collaboration features as well.

For how long have I used the solution?

I've been using the solution for at least seven years.

What do I think about the stability of the solution?

The solution is stable.

What do I think about the scalability of the solution?

The scalability is a little bit complex. We do have a lot of issues with scalability. It's not everything we hoped for.

How are customer service and technical support?

We go through our own IT department, so we don't deal with technical support directly.

Which solution did I use previously and why did I switch?

I'm not aware of our organization using a different solution. We've always used SharePoint Designer.

How was the initial setup?

For our organization, it was quite complex. We have different departments in our group that require different access, which added a layer of complexity for us. The deployment took about a year.

What other advice do I have?

We use the on-premises deployment model.

A lot of planning is necessary before deciding on a final solution or a final architecture. Planning is very important prior to implementation.

I'd rate the solution seven out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
MB
SharePoint Developer
Real User
Feature-rich and good for development, but can be made easier to use

What is our primary use case?

I use this solution for site development.

What is most valuable?

The most valuable feature is the development.

What needs improvement?

This solution could definitely be made easier to use.

For how long have I used the solution?

I have been using this solution for almost five years.

What do I think about the stability of the solution?

This solution runs alright.

How are customer service and technical support?

The technical support for this solution is fair. It's ok.

How was the initial setup?

The initial setup of this solution is straightforward.

What's my experience with pricing, setup cost, and licensing?

This solution is free of charge.

What other advice do I have?

This product basically has all of the features that I need,…

What is our primary use case?

I use this solution for site development.

What is most valuable?

The most valuable feature is the development.

What needs improvement?

This solution could definitely be made easier to use.

For how long have I used the solution?

I have been using this solution for almost five years.

What do I think about the stability of the solution?

This solution runs alright.

How are customer service and technical support?

The technical support for this solution is fair. It's ok.

How was the initial setup?

The initial setup of this solution is straightforward.

What's my experience with pricing, setup cost, and licensing?

This solution is free of charge.

What other advice do I have?

This product basically has all of the features that I need, but there is no such thing as a perfect solution.

I would rate this solution a seven out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
KM
Cloud Solution Architect at a tech services company with 1-10 employees
Real User
The workflow is good but there are small issues that need to improve

Pros and Cons

  • "The feature I find most valuable, is the workflow of the product."
  • "I am not sure how stable the solution will be once Microsoft stops supporting it."

What is most valuable?

The feature I find most valuable, is the workflow of the product. I have used it in the past to design different teller sellers, automating the business process using the workflows.

What needs improvement?

I think the product will soon not be supported anymore due to the new way of using those components in Microsoft flow and power apps. I have heard that Microsoft is not going to lease SharePoint Designer anymore.

For how long have I used the solution?

I have been using the solution for ten years now.

What do I think about the stability of the solution?

I am not sure how stable the solution will be once Microsoft stops supporting it.

What other advice do I have?

On a scale from one to ten, I rate this solution a seven. I like the user experience level and there were some small issues, but I can't remember what they were. It was a long time ago. If Microsoft will keep on supporting the program, they should fix those small issues.  

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
JJ
Business Solutions Architect at a real estate/law firm with 501-1,000 employees
Real User
Top 20
The solution needs a modern deployment and should offer a development environment instead of a customization tool

Pros and Cons

  • "The most valuable part of the solution is its ability to allow for a high degree of customization."
  • "The solution is not scalable at all."

What is our primary use case?

We primarily use the solution for modifying SharePoint.

What is most valuable?

The most valuable part of the solution is its ability to allow for a high degree of customization.

What needs improvement?

Many aspects of the solution need improvement. It does not make use of modern deployment. You should also be able to separate your concerns between the code and the environment. It should become a development environment rather than a customization tool.

For how long have I used the solution?

I've been using the solution for ten years.

What do I think about the stability of the solution?

Recently, the stability of the solution has been okay. The later versions have been better.

What do I think about the scalability of the solution?

The solution is not scalable at all.

What other advice do I have?

In terms of advice I would give to others considering implementing the solution, I would say they should adopt the SharePoint Framework and do it with Visual Studio.

I'd rate the solution three out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
SD
Technical Coordinator at a manufacturing company with 10,001+ employees
Real User
Great features but I would like to be able to create more complicated designs

Pros and Cons

  • "The new version doesn't have the option to view data, but it has other, better features though."
  • "I would like to be able to use SharePoint Designer without having to buy other third party programs."

What is most valuable?

The previous version of the solution was good as we had different views of both the design and the code. The new version doesn't have the option to view data but it has other, better features though.

What needs improvement?

I would like to see some improvements when assigning a task. For instance, when you create a task or a subtask, there should be a better workflow. At this stage, we can't CC any names in the sent box. We can only use a "to" address. So when I want to send an email, I have to write a custom code through .NET and then send the mail. It takes up a lot of my time. Then I also found that there was a requirement from one of my customers that they want this option in the taskbar too. For instance, when the email gets sent, they want a CC option as well. 

What other advice do I have?

I will rate this program a five out of ten. The reason for this is that I would like to be able to use SharePoint Designer without having to buy other third party programs. At this stage, I still have to use other designing webpages because SharePoint Designer doesn't offer all the features I need. You can create beautiful pages, add the list and add a document library, but the solution doesn't offer any complicated designing features. One can only do a few simple designs. Everything has to be coded through either Visual Studio or some other solution. So I hope to see an improvement in the new version of this program. Perhaps they can add different templates where one can add banners, tabs, and lists. And even drag and drop features where one can add permissions. That would be great. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
OA
SharePoint Developer at Zak solutions
Real User
Ability to create HTML pages is helpful for our projects

Pros and Cons

  • "Other valuable features are the ability able to update the master file, and creating the workflow."
  • "If you compare the workflow with other engines like Olympus and K2, it is very complicated to create a workflow."

What is most valuable?

The most valuable feature is the capability of creating HTML pages, with CSS code. For example, most of the time I mirror in the web area, which means that I need to create an HTML file. Inside this HTML file I will write my web VBI.

Other valuable features are the ability able to update the master file, and creating the workflow.

What needs improvement?

Sometimes when I create my HTML page it is very slow and I don't know why. It's just stuck. I think that the performance needs to be enhanced.

If you compare the workflow with other engines like Olympus and K2, it is very complicated to create a workflow.

In the next release, I would like ready-made workflows that I can re-use and a way to apply a design for the master base that is less complicated.

For how long have I used the solution?

I have been using this solution for twelve years.

What do I think about the stability of the solution?

This solution is stable.

How are customer service and technical support?

I have not contacted technical support. With twelve years of experience, I can resolve the issues.

How was the initial setup?

The deployment is used for both private and public clouds.

What other advice do I have?

I would rate this solution a nine out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
RI
Consultant at a comms service provider with 201-500 employees
Consultant
A solution with a straightforward setup that's great for designing workflows but has limited scalability

Pros and Cons

  • "The initial setup is straightforward."
  • "The web services aspect of the solution is very weak."

What is most valuable?

The solution's best feature is designing workflow processing. It's easy to change and collate workflows.

What needs improvement?

The solution has limitations when it comes to exploration.

The web services aspect of the solution is very weak.

If the requirements are moderate, the solution is okay, but for more complex requirements, I need to use the solution in combination with other solutions. It doesn't offer everything I need.

For how long have I used the solution?

I've been using the solution since 2012.

What do I think about the stability of the solution?

The stability is okay but limited.

What do I think about the scalability of the solution?

The scalability is okay but limited.

How was the initial setup?

The initial setup is straightforward.

What other advice do I have?

We're using the SharePoint 2000 version.

The solution makes the work of estimating the requirements pretty difficult. Mainly, it is a very useful tool I can use for small to medium requirements.

If you're new to the solution, be aware that Sharepoint can be challenging, so you need to be ready to learn the solution in order to fully use it. Sharepoint involves coding; it's not like other solutions that offer zero coding. Organizations considering implementing it should be made aware of this.

If you are considering implementing it, I'd take the time to compare it to what you already have and any other options you are considering so that you are able to choose the solution that will work best for you. There are a lot of features now that are actually offered by competitors.

I'd rate the solution seven out of ten. If you were talking about the 2016 version, I'd give it a seven out of ten, but the 2013 version I would rate a six.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
AE
Technical Director at wbn
Real User
An excellent document filing solution offering creative solutions to document management

Pros and Cons

  • "The document filing system is the solution's most valuable feature. We have used SharePoint as an option for a document managed system, like Documentum and IBM Filenet."
  • "I believe Microsoft does not support Sharepoint on-premises. They only support Sharepoint on the Cloud. They should provide for both options and let the client choose their preference."

What is our primary use case?

We primarily use the it as a creative solution for document management.

What is most valuable?

The document filing system is the solution's most valuable feature. We have used SharePoint as an option for a document managed system, like Documentum and IBM Filenet.

What needs improvement?

I believe Microsoft does not support Sharepoint on-premises. They only support Sharepoint on the Cloud. They should provide for both options and let the client choose their preference.

The solution should have a better workflow with the craft, and also offer some configurations to help drive workflow.

For how long have I used the solution?

I've been using the solution for five years.

What other advice do I have?

I'd rate the solution eight out of ten.

There are other solutions on the market. Some are more usable than Sharepoint.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
BP
Solutions Manager - Collaborative Platform at a manufacturing company with 10,001+ employees
Real User
A solution that offers good workflows, but is a bit complex

What is most valuable?

The workflow is the solution's most valuable feature.

What needs improvement?

The solution is a bit complex. They should work to simplify it. 

For how long have I used the solution?

I've been using the solution for two years.

How was the initial setup?

The initial setup is complex.

What other advice do I have?

We're using the 2013 version of the solution. The solution has a lot of complexity. That might work for some people, depending on the use case, but for others, that may be a turn-off. I would rate the solution seven out of ten. I'd rate it higher, but there are other solutions that are able to better cover my needs.

What is most valuable?

The workflow is the solution's most valuable feature.

What needs improvement?

The solution is a bit complex. They should work to simplify it. 

For how long have I used the solution?

I've been using the solution for two years.

How was the initial setup?

The initial setup is complex.

What other advice do I have?

We're using the 2013 version of the solution.

The solution has a lot of complexity. That might work for some people, depending on the use case, but for others, that may be a turn-off.

I would rate the solution seven out of ten. I'd rate it higher, but there are other solutions that are able to better cover my needs.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Ghislaine-Resplandy
Office 365 Specialist at a energy/utilities company with 51-200 employees
Real User
A stable solution that's easy to set up and has a good user interface

Pros and Cons

  • "The most valuable aspects of the solution are the user-friendly interface and easy workflow."
  • "Further development for SharePoint online would be ideal. However, I'm not sure if it's true that Microsoft will no longer develop SharePoint Designer in the future or not."

What is our primary use case?

I use it mainly for workflows or for minor changes in SharePoint master pages.

How has it helped my organization?

I have setup many simple and complex workflows, very useful for daily automation (invoices, travel, leave approval) . It is also useful to make small branding customizations.


What is most valuable?

The most valuable aspects of the solution are the user-friendly interface and easy creation of workflow. 

What needs improvement?

Unfortunately Microsoft announced a few years ago that the last update for SharePoint Designer was released on August 2, 2016 and that Microsoft Flow will be the workflow designer and engine going forward.


I would add Nintex or all of the Nintex workflow to the solution if I could. I would add them to SharePoint Designer so that I would need to use only one workflow designer. Right now, I'm using SharePoint Designer and Nintex, and it would be better to centralize it.

For how long have I used the solution?

I've been using the solution for ten years.

What do I think about the stability of the solution?

The solution is stable.

What do I think about the scalability of the solution?

SharePoint Designer is a very small tool, and very clever. You install it on your computer to access SharePoint's entire platform. In that sense, it's not a technology that's scalable or that needs to be scalable.

How are customer service and technical support?

I've never had to contact technical support.

How was the initial setup?

The initial setup is very easy. Deployment takes five minutes; it's basically just installing the software. 

What about the implementation team?

I deployed the solution myself.

What other advice do I have?

We use the on-premises deployment solution.

I'd rate the solution eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
TA
Senior Consultant at SPEEDNET LIMTED
Consultant
We can use it as a secondary customization platform but it should be more flexible and upgrading should be simpler

Pros and Cons

  • "What I like most about this solution, is that we can use it as a secondary customization platform."
  • "There is zero technical support. I have to use Google to fix the issues myself."

What is our primary use case?

Our primary use case for SharePoint Designer is for implementation for clients.

What is most valuable?

What I like most about this solution, is that we can use it as a secondary customization platform. We do customization and make a web SharePoint live for our clients. 

What needs improvement?

From what I read online, it depends on what you use the program for. I think the customization and migration need to improve. Upgrading should be simpler without too many things you need to change or repair. 

SharePoint Designer should be more practical and become an extension of Visual Studio. Because Visual Studio is a universal development platform. So I don't want to have to switch my user ID every time. So it should be more flexible and more of a mobile app version and integration with other solutions.  

For how long have I used the solution?

I've been using SharePoint Designer for more than six years now on premise.

What do I think about the stability of the solution?

The program is perfectly stable. I really like Microsoft products because they are very advanced. I like SharePoint because it's big and the pricing is fair. 

What do I think about the scalability of the solution?

The scalability of SharePoint is good and the program is fast. 

How are customer service and technical support?

There is zero technical support. I have to use Google to fix the issues myself.

Which solution did I use previously and why did I switch?

I used a smaller content management platform which I customized. Visual Studio and SharePoint Designer work well together and could be extensions to each other.

How was the initial setup?

I struggle with the installation. We are not a small company and there are three equal sides. You need to get them right, otherwise, SharePoint won't install properly. A single installation takes a couple of hours. You need time to do separate functionality. 

The program wasn't easy to deploy either, because when I integrate solutions, I have to do so many things before I can deploy SharePoint. So the process is a little tedious due to the security features of the program, but once you get it, it becomes easier. But its always a challenge for someone who is unfamiliar with this program. 

What's my experience with pricing, setup cost, and licensing?

I've never paid for SharePoint Designer. What I paid for is the SharePoint license, the cava, and then the client accesses the line fee. 

What other advice do I have?

On a scale of one to ten, I rate this a five because it could be more flexible.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.