How to Remove Weekends From an MS Project Gantt Chart [2026]

Weekend shading can make an MS Project Gantt chart look longer and more complicated than it really is. Your tasks may still have the correct durations, yet the timeline appears packed with gray Saturday and Sunday columns.

That creates practical problems. Stakeholders may think work continues over the weekend, exported schedules become harder to read, and milestone reviews can focus on calendar shading instead of delivery dates.

But here's the truth: you usually do not need to change task durations or delete weekends from the project calendar. You can hide nonworking time in the Gantt chart while keeping scheduling rules intact. The steps below show how to do it safely in MS Project in 2026.

How to Hide Weekends From an MS Project Gantt Chart

To remove weekends visually from an MS Project Gantt chart, open the Timescale settings, select the Non-Working Time tab, and set the display option to “Not shown.” This hides weekend shading without changing task dates or working-time rules.

1. Open the Gantt Chart view

Start MS Project and open the schedule you want to adjust. Select Gantt Chart from the View tab if another view is currently active.

Make sure the timeline displays the weekend columns you want to hide. If the timescale is too compressed, zoom in until you can clearly see the daily or weekly calendar structure.

2. Open the Timescale dialog

Go to the Format tab on the ribbon. In the Timescale group, select the small dialog launcher in the lower-right corner.

Depending on your MS Project version, you may also be able to right-click the timescale at the top of the Gantt Chart and select Timescale.

3. Select Non-Working Time

In the Timescale dialog box, open the Non-Working Time tab. This area controls how weekends, holidays, and other nonworking periods appear behind the task bars.

Look for the display setting labeled Show or a similar option under the nonworking-time formatting controls.

4. Choose “Not shown”

Set the display option to Not shown. This removes the visual shading for nonworking periods from the Gantt Chart view.

Click OK to apply the change. Saturday and Sunday should no longer appear as shaded areas behind the schedule.

5. Check the schedule dates

Review several tasks after applying the setting. Confirm that their start dates, finish dates, durations, and dependencies remain unchanged.

This check matters because hiding weekend shading only changes presentation. It should not convert Saturday and Sunday into working days.

6. Save the view for future use

If you regularly present schedules without weekend shading, save the adjusted view or add it to a reusable project template.

For a recurring reporting process, keep one presentation view with weekends hidden and another planning view that displays nonworking time. That gives you a clean executive view without losing calendar visibility during detailed planning.

What This Setting Changes—and What It Does Not

The Timescale setting changes how nonworking periods are drawn on the chart. It does not alter the project calendar, task constraints, resource availability, or dependency calculations.

For example, a five-day task starting on Monday can still finish on Friday. A task starting on Friday may still continue into Monday if its duration requires more working time.

Here's why: MS Project separates scheduling logic from chart formatting. The calendar determines when work can occur, while the Timescale settings determine how that calendar appears.

Do not change the working calendar by mistake

If your goal is only to clean up the visual layout, avoid using Project > Change Working Time. That command changes scheduling behavior.

Changing Saturday and Sunday to working days can move task finish dates, affect resource allocation, and change the critical path. Use that command only when weekend work is genuinely part of the plan.

How to Keep Weekends as Nonworking Days

Most project schedules should continue treating weekends as nonworking days. You can hide their visual shading while preserving that rule.

For example, imagine a construction activity with a three-day duration beginning Thursday. If Saturday and Sunday remain nonworking, MS Project will schedule the work across Thursday, Friday, and Monday. Hiding the gray weekend area does not change that result.

You might be wondering: why hide weekends at all? A clean chart often works better for steering meetings, especially when the audience cares about milestones and work packages rather than daily calendar detail.

Use the standard project calendar

Open Project > Change Working Time and confirm that the selected project calendar matches your intended schedule. The standard calendar commonly treats Monday through Friday as working days.

Review exceptions and holidays

Check the calendar’s exceptions area for public holidays, shutdowns, company events, or planned maintenance periods.

Hiding nonworking shading can make these exceptions less visible. Keep a separate planning view or calendar review process so important closures are not overlooked.

Check task and resource calendars

A task can use a different calendar from the overall project. A resource can also have individual availability rules.

For instance, a laboratory task may follow a seven-day calendar while the rest of the project follows a five-day schedule. The chart can look clean while task-level rules still control the dates.

When Hiding Weekends Is Useful

Weekend removal is especially helpful when the chart is used for communication rather than detailed scheduling. A client-facing milestone plan usually benefits from less visual noise.

Consider a software release schedule with 40 tasks. If every Saturday and Sunday is shaded, the timeline may look crowded even though most work occurs Monday through Friday. Removing the shading makes the delivery sequence easier to scan.

The best part? You can retain the accurate schedule underneath. Planners still see correct finish dates, while executives get a cleaner view of progress and risk.

Executive status reviews

Leadership teams often need a quick view of upcoming milestones, delayed work, and major dependencies. Weekend shading rarely helps answer those questions.

Client presentations

Clients may interpret shaded periods as active work or downtime. A simplified chart reduces unnecessary questions during a presentation.

Printed schedules

Heavy shading can reduce contrast when a chart is printed in grayscale. Hiding nonworking periods can make task bars and milestone symbols easier to distinguish.

High-level roadmap views

When the timescale shows weeks or months, individual weekend columns add little value. A cleaner timeline keeps attention on phases, releases, and key dates.

How to Troubleshoot Weekend Display Problems

If weekends remain visible, the setting may not have been applied to the active view. Check that you are editing the Gantt Chart Timescale rather than a different view.

Weekend shading is still visible

Reopen the Timescale dialog and confirm that Not shown is selected under Non-Working Time. Click OK, then refresh the view by switching to another view and returning to Gantt Chart.

The dates changed after your edit

You may have changed working time instead of chart formatting. Open the project calendar and compare its working days with the earlier configuration.

Review task start and finish dates, then check whether any resources or tasks use special calendars. Restore the calendar settings before changing the display option again.

Only some weekends appear hidden

Different views can have different Timescale settings. A custom view, saved report, or separate project plan may still display nonworking periods.

Apply the setting to each view used for reporting. Also check whether a custom background style is creating the appearance of weekend shading.

Holidays are no longer obvious

When all nonworking time is hidden, holidays may blend into the rest of the timeline. Keep holiday details in a calendar review, task note, milestone list, or planning view.

Managing Project Schedules With ONES.com

ONES.com is a unified platform for project management and knowledge management, powered by ONES Assistant. ONES Project is the project management product and can serve as a Jira alternative for teams that need structured planning, reporting, and workflow control.

It can help when your team wants a readable schedule, consistent work rules, and project information in one workspace. ONES Project is sold separately from ONES Wiki, the knowledge management product and Confluence alternative.

Value Proposition

ONES.com helps project teams organize plans, workflows, progress updates, and delivery knowledge without relying on a large collection of plugins. You can use Cloud, On-Premise, Private Cloud, or Air-gapped deployments, with full feature parity between cloud and self-hosted versions.

Core Capabilities

Weekend and calendar confusion → Custom workflows and fields → Clearer schedule context

When calendar rules are difficult to explain, teams can add fields for working pattern, release window, holiday treatment, or delivery risk. That context helps reviewers understand why a date falls where it does.

Scattered progress updates → Built-in reporting → Faster status reviews

Manual status collection can delay decisions. Built-in reporting gives project leads a consistent way to review progress, overdue work, milestones, and delivery trends.

Rigid planning routines → Sprint management → More predictable iteration planning

Teams using iterative delivery can organize work into sprints, track commitments, and review completed work in a repeatable workflow.

Manual handoffs → Automation → Fewer repetitive updates

Automation can support recurring transitions, notifications, assignments, and approval actions. That reduces the chance of a task remaining in the wrong status after a handoff.

Multiple plug-ins → Native project capabilities → Lower workflow complexity

Jira-compatible workflows, reporting, custom fields, sprint management, and automation are available within the project environment. Teams can reduce dependence on separate extensions for common planning needs.

Restricted network requirements → On-Premise or Air-gapped deployment → Greater environment control

Organizations with strict security or network policies can choose a self-hosted deployment. This supports teams that cannot place project operations entirely in a public cloud.

Disconnected project knowledge → ONES Wiki integration → Easier knowledge discovery

Project decisions and delivery guidance can be organized alongside project work. ONES Wiki is available separately for teams seeking a Confluence alternative.

Growing AI adoption → Tiered AI usage model → A more controlled path to team-scale use

ONES.com provides a three-layer approach for AI-supported work. The basic allowance gives you a low-barrier way to try core AI features and handle limited requests.

Assistant Credit provides 3,000 credits per user per month in addition to the basic allowance. When individual credits are insufficient, Extra Credit provides a team-shared pool for higher-frequency usage and broader adoption.

Extra Credit costs USD 10 per 1,000 credits, with a minimum order of 5,000 credits. It is not unlimited. The model supports a practical move from individual experimentation to stable personal use and then team-scale adoption.

Application Scenarios

Scenario 1: A distributed product team

A product team works across several regions and needs consistent sprint planning. It can use custom workflows, sprint management, and reporting to make delivery status easier to compare across teams.

Scenario 2: A regulated engineering organization

An engineering group cannot place project operations on a public cloud. An On-Premise, Private Cloud, or Air-gapped deployment can support its environment requirements while preserving core platform capabilities.

Scenario 3: A team adopting AI gradually

A small group can begin with the basic allowance, use Assistant Credit for regular individual work, and add team-shared Extra Credit when frequent AI requests exceed personal availability.

Common Challenges and Practical Solutions

Challenge: You hide weekends and lose useful planning context

Solution: Maintain two views. Use one clean presentation view for stakeholders and another planning view that shows nonworking time, holidays, and calendar exceptions.

Challenge: Stakeholders think hidden weekends mean continuous work

Solution: Add a note to the report stating that weekends remain nonworking days. Include the project calendar name and the schedule’s working pattern in the legend.

Challenge: The chart is still difficult to read

Solution: Adjust the timescale, reduce unnecessary columns, filter completed tasks, and group work by phase. Hiding weekends helps, but it may not solve overcrowding by itself.

Challenge: Different teams use different calendars

Solution: Record the calendar applied to each major workstream. Review task and resource calendars before comparing dates across teams.

Challenge: AI usage grows beyond individual allowances

Solution: Use the three-layer ONES.com model deliberately. Start with the basic allowance, rely on Assistant Credit for regular individual activity, and add Extra Credit for team-shared demand.

FAQs About Hiding Weekends in MS Project

Does hiding weekends remove them from the project schedule?

No. The setting only changes how nonworking periods appear in the Gantt Chart. Saturday and Sunday remain part of the calendar, and MS Project continues using the selected working-time rules when it calculates task dates.

Will task durations change when I set nonworking time to “Not shown”?

No. Task durations, dependencies, start dates, and finish dates should remain the same. If dates change, check whether you accidentally edited the project, task, or resource calendar instead of the Timescale display settings.

Can I hide weekends but keep holidays visible?

MS Project generally controls nonworking-time display as a group. If you hide all nonworking periods, holidays may also become less visible. Keep a separate calendar review or planning view when holiday awareness matters.

Why do weekends still appear in another project view?

Timescale formatting can differ between views. A custom Gantt Chart, tracking view, or saved report may use different settings. Open the relevant view and adjust its Non-Working Time display separately.

Should I change Saturday and Sunday to working days?

Only when the team genuinely performs planned work on those days. Changing them to working days affects scheduling calculations and can move task dates. If you only want a cleaner chart, use the “Not shown” display option.

Can ONES.com replace MS Project for teams that need structured project workflows?

ONES Project can serve as a Jira alternative for teams seeking project planning, custom workflows, reporting, sprint management, automation, and controlled deployment options. Evaluate calendar behavior, reporting needs, migration requirements, and team workflows before selecting a platform.

Conclusion

To hide weekends from an MS Project Gantt chart, open the Timescale settings, select Non-Working Time, and choose Not shown. This cleans up the visual timeline without changing the project’s scheduling rules.

Keep weekends configured as nonworking unless your team truly plans weekend activity. Use a second planning view when holidays, shutdowns, or unusual calendars require closer attention.

But here's the truth: a readable chart is only useful when its calendar logic remains accurate. Separate presentation formatting from scheduling decisions, check task and resource calendars, and explain hidden weekends to your audience.

If your team needs a broader project workspace, ONES.com offers ONES Project with Jira-compatible workflows, reporting, automation, sprint management, custom fields, and deployment choices that include On-Premise and Air-gapped environments.