1
00:00:00,080 --> 00:00:04,206
A full Gmail account can contain large messages that are hard

2
00:00:04,206 --> 00:00:05,706
to spot by scrolling.

3
00:00:05,706 --> 00:00:09,832
We will search for messages that both contain an attachment and

4
00:00:09,832 --> 00:00:12,457
exceed ten megabytes in total message size.

5
00:00:12,457 --> 00:00:16,958
The result is a review list, not an instruction to delete everything.

6
00:00:16,958 --> 00:00:22,959
A fictional four-message index lets us check the search logic without exposing anyone's inbox.

7
00:00:23,559 --> 00:00:26,243
The practice file lists four fictional messages.

8
00:00:26,243 --> 00:00:29,694
Two have attachments and total sizes above ten megabytes.

9
00:00:29,694 --> 00:00:33,912
One has an attachment but is only two megabytes; another is

10
00:00:33,912 --> 00:00:35,829
large but has no attachment.

11
00:00:35,829 --> 00:00:39,664
Predict which two should match before using the search box.

12
00:00:39,664 --> 00:00:43,881
That prediction gives you a real answer check even if your

13
00:00:43,881 --> 00:00:45,799
account contains no suitable messages.

14
00:00:46,399 --> 00:00:51,478
In Gmail's search box, enter has colon attachment, a space, then

15
00:00:51,478 --> 00:00:53,595
larger colon ten capital M.

16
00:00:53,595 --> 00:00:57,404
Written exactly, the query is `has:attachment larger:10M`.

17
00:00:57,404 --> 00:01:02,907
Google documents each operator and says search operators can be combined. Press Enter.

18
00:01:02,907 --> 00:01:07,140
The result list should contain only messages satisfying both conditions;

19
00:01:07,140 --> 00:01:10,949
use your own account only for the interface demonstration.

20
00:01:11,549 --> 00:01:17,121
The size filter applies to an email message, not independently to every attached file.

21
00:01:17,121 --> 00:01:21,897
A twelve-megabyte message may contain a smaller attachment plus message overhead.

22
00:01:21,897 --> 00:01:27,071
That distinction prevents a misleading title such as attachments larger than ten megabytes.

23
00:01:27,071 --> 00:01:31,449
The query is a useful candidate finder, but inspect the message

24
00:01:31,449 --> 00:01:35,031
and its attachments before deciding whether to keep it.

25
00:01:35,631 --> 00:01:39,660
Open a result and check sender, date, subject, and whether the

26
00:01:39,660 --> 00:01:41,125
attachment is still needed.

27
00:01:41,125 --> 00:01:44,787
A message can be important even if it is large.

28
00:01:44,787 --> 00:01:48,815
If you plan a storage cleanup later, save or document what

29
00:01:48,815 --> 00:01:50,280
must be retained first.

30
00:01:50,280 --> 00:01:53,942
This lesson deliberately stops at finding and reviewing candidates; it

31
00:01:53,942 --> 00:01:57,605
does not empty Trash or promise an immediate storage increase.

32
00:01:58,205 --> 00:02:03,480
If no messages appear, the query may simply have no match in that account.

33
00:02:03,480 --> 00:02:07,625
Try a smaller threshold for exploration, for example larger colon five

34
00:02:07,625 --> 00:02:10,263
capital M, while keeping has colon attachment.

35
00:02:10,263 --> 00:02:14,408
Do not interpret zero results as proof that all large attachments

36
00:02:14,408 --> 00:02:18,930
are gone: Gmail's size test concerns complete messages and the result

37
00:02:18,930 --> 00:02:22,321
also depends on what is retained in the account.

38
00:02:22,921 --> 00:02:25,627
Compare your prediction with the practice index.

39
00:02:25,627 --> 00:02:31,038
M-102 and M-104 satisfy both conditions; M-101 is under the threshold

40
00:02:31,038 --> 00:02:33,356
and M-103 lacks an attachment.

41
00:02:33,356 --> 00:02:36,835
The video and guide stop with a review list.

42
00:02:36,835 --> 00:02:41,473
If you later remove messages, use Gmail's own storage information to

43
00:02:41,473 --> 00:02:45,724
verify any change rather than assuming that a search or a

44
00:02:45,724 --> 00:02:47,657
move to Trash freed space.
